Hafrix resources
Bring the records across. Keep the work understandable.
Choose a detailed migration guide for RigER, Asset Patrol, Rentman, Bynder DAM or spreadsheets. Plan exports, mapping, reconciliation, a pilot and cutover.
Moving systems starts with the operation you need to preserve: equipment already on hire, the next warehouse handover, the first billing review or the approved product file a partner needs. Use the guide for your source system to prepare the data, decisions and checks for that move.
Choose your source system
| Source | What the guide covers | Detailed guide |
|---|---|---|
| RigER | Equipment identities, active rentals, repair history, certificates and the boundary between historical and new billing | Move from RigER |
| Asset Patrol | Oil-tool tracking, rental statuses, specialist rate bases, inspection records and the QHSE/accounting boundary | Move from Asset Patrol |
| Rentman | XLSX exports, catalogue items versus serial units, combinations, open projects, partial returns and commercial records | Move from Rentman |
| Bynder | Original files, metadata, product and language context, revisions, usage rights, access and downstream links | Plan a Bynder DAM migration |
| Excel and other spreadsheets | Starting registers, identifiers, duplicates and a controlled opening position | Move from spreadsheets |
Bynder is a DAM workflow with its own pilot and acceptance criteria. Its digital files and rights are assessed separately from the equipment and rental records in the other guides. Confirm the Hafrix functions available for your pilot before committing to a replacement.
What to prepare before the first discussion
Describe the source system and the modules you use, approximate record or file volumes, the operation that must keep running and the person responsible for approving the move. Include essential integrations and one difficult example, such as a partial return, an invoice adjustment or a restricted file.
The first step is an assessment of a representative export. After contact, agree the sample, transfer method, access and retention period. Send no passwords, API secrets or confidential data through the public enquiry form.
Agree what a successful move means
Before a final transfer, agree the source-to-target mapping, historical scope, exception owners and evidence for acceptance. Rehearse the actual task with the people who will do it. Check record relationships, quantities or files and access as well as headline counts.
For equipment operations, reconcile open commitments and the billing boundary. For DAM, verify originals, context, rights and distribution dependencies. Keep a recovery plan that accounts for work entered after the switch.
Exports and supported transfer methods depend on your source version, configuration and agreed target setup. These guides describe a controlled implementation process; they do not promise an automatic connector, universal import, fixed duration or feature-for-feature replacement. Timing and cost follow assessment of your actual scope.
Discuss your migration · Explore Hafrix workflows · Review data and access
Keep the context
Make it workfor your team.
Talk through the equipment, people and records behind your day-to-day work.
Talk to Hafrix