Service OS Pro
Move the operating record without pretending every source is clean.
Start with the records required for the first live workflow. Test a dry run, surface duplicates and missing fields, review exceptions, and decide the cutover deliberately.
- 1Source inventory. List where the operating record actually lives today — the platform, the spreadsheets, the texts.
- 2What moves first. Start with the records required for the first live workflow, not the whole history.
- 3Dry run. Test an import, surface duplicates and missing fields, and read the exceptions before anything is final.
- 4Exception ownership. Every record that cannot move cleanly gets a named owner and a decision — fix, defer, or leave behind.
- 5Training and parallel period. The team runs the new system on real work while the old one is still there to check against.
- 6Go-live. Cut over deliberately, on a chosen day, with the fallback still warm.
What each source supports today.
Housecall Pro supports a direct read-only API import for customers, jobs, invoices, estimates, and the price book; memberships and service plans move by CSV. Jobber and ServiceTitan are CSV paths today — no direct connector exists or is implied.
A migration plan is not a promise that every historical record, custom field, or third-party dependency will move unchanged.