How do you switch rental software without losing open jobs?
Start with an inventory of what must move: equipment, customers, rates, open jobs and outstanding balances. Test a small import and reconcile quantities and active commitments before moving the full operation. If you use a parallel run, define which system owns each update so work is not duplicated. Retire the old system only after the next jobs, availability and balances have been checked and a rollback plan exists.
Agree on the cutover boundary
List the records that affect work after the changeover: catalog items, warehouses, stock states, customers, active quotes, confirmed jobs, outstanding returns and financial balances. Give each type a named owner. Decide which system is authoritative for each record during the transition so two teams do not update two different versions.
Do not assume every historical attachment belongs in the new system. Define retention and access requirements with the appropriate advisers, then choose what to migrate and how the remaining archive can be searched. Keep exports and mapping notes protected; a convenient migration folder should not become an uncontrolled store of customer information.
Rehearse a complete fictional job
Use a test workspace with invented records. Acme Demo Co quotes ten Category A units, changes the quantity to 12, dispatches them, receives 11 and places one on an unresolved-return record. The office then reviews what is billable. Follow that sequence in the proposed setup.
Check more than screen appearance. Do warehouse assignments survive? Are dates interpreted in the correct time zone? Can the team distinguish available stock from damaged stock? Can an approved change be found from the job? Are document references understandable? Record each mismatch and who will resolve it.
Reconcile totals and exceptions
Compare counts by category and warehouse, not just a grand total. A fleet total can match while two warehouses are reversed. Reconcile open customer balances and job commitments separately. Explain excluded records and intentional differences in a signed-off migration record instead of forcing totals to agree through undocumented adjustments.
For cutover, define the export time, the final reconciliation, the first live job and the person who can decide to pause. Write a rollback plan before starting. If transactions occur after the first export, decide how the changes will be captured and checked before the new system becomes authoritative.
The practical acceptance test is straightforward: the warehouse can prepare the next job, dispatch can find its instructions, the office can explain the balance and the team knows where to record an exception. Ssabi is in early access; confirm migration scope and support arrangements in a demo before planning a live changeover.