Spreadsheet imports
Map supported CSV columns to equipment fields, review validation findings and apply a checked import.
Integrations & imports
Bring the source.Keep the connection clear.
Connect the records your operation relies on. Start with a defined source, a reviewed mapping and a way to explain what changed.
Choose the starting point
Different sources.One reviewed process.
An import, an operating-data connection and a new integration each need their own scope. Begin with the path that fits the records you have.
Move from spreadsheets
Existing-system exports
Assess authorized exports, identifiers, open work and the history that should move with the operation.
Operating data from beat
Use the supported beat connection for source records such as rigs, wells, companies and equipment activity.
Review the connection
Match with care.Keep the evidence.
A connection is useful when the team understands how source records relate to the equipment and work in Hafrix.
Identify the record
Agree stable identifiers, units and the meaning of source fields before combining datasets.
Review uncertain matches
Confirm or reject supported matching suggestions. Keep ambiguous records visible for a person to resolve.
Follow the source status
Review the supported connector’s status and synchronization results before relying on a new set of records.
Before a new connection
Name the workflow.Define the responsibility.
Bring a sample and the decision it needs to support. Agree the source contract and ownership before implementation.
Data and direction
Identify which records move, where they originate and whether the workflow reads information or also needs to write it.
Access and ownership
Agree authorization, source-system access and who reviews mapping and reconciliation exceptions.
Reconciliation and support
Define how the team checks the result, handles an unavailable source and knows where to ask for help.
Is there a connector for every external product?
No. The supported source and the required workflow must be reviewed. A product name on a requirements list does not establish a ready-made integration.
Does migration from RigER require a live connector?
The migration approach is based on authorized exports and an agreed mapping. A live RigER connector or access to its private database is not promised.
What should we bring to an integration discussion?
A representative sample, available source documentation, the records you need to move and the person who can approve the resulting data.
Show us the source.Explain the next decision.
Start with the records and the workflow you want to connect.
Discuss an integration