Choose the workflow
Start with a real equipment move, rental, service task or billing review that the team can follow from beginning to end.
Onboarding
Start with your records.Finish a real job.
Bring the people who own the data and the people who use it. Build the workspace around a representative workflow, then agree the move into daily operation.
01 / Set the scope
Know the starting point.Agree the first result.
Choose a useful first workflow and define the records, responsibilities and access needed to complete it.
Explore workflows
Name the data owners
Identify the people who can confirm equipment, locations, customers, documents and opening records.
Set up the team
Review users, roles and the product areas each person needs for the first workflow.
02 / Review the records
Work with a sample.Resolve the exceptions.
Start small enough to inspect. Include difficult records as well as clean ones so the review reflects the real operation.
Map the source
Review identifiers, duplicate serials, units, dates and locations. Agree which source is authoritative when files disagree.
Check representative records
Use serialized equipment, stock, attached documents and open work to check the agreed import scope.
Reconcile with the owners
Compare counts, locations and opening values with the source. Record the decisions needed before applying the final dataset.
03 / Put the work in motion
Rehearse the handover.Then agree the switch.
The first complete task is the acceptance test for the people who will use the workspace.
Practice by role
Let the rental desk, yard, field and office complete their own part of the same sample workflow.
Agree the cutover
Set the final export, any freeze or catch-up window, reconciliation checks and the people who can approve the switch.
Keep help close
Use the relevant documentation and Care conversation when the first live questions arrive.
How long does onboarding take?
The schedule follows the agreed scope, source-data condition, required integrations and the team’s availability. We agree it after reviewing representative records.
Do we need to start with every module?
No. Start with the workflow and modules the pilot needs, while preserving the context that the next team will use.
What happens to history outside the import scope?
Agree what must be carried forward and what can remain in a retained source archive. Historical depth, attachments and opening balances are explicit parts of the migration scope.
Bring the first workflow.Build the starting plan.
Discuss the records, people and acceptance checks that will make your first useful task possible.
Plan your onboarding