TL;DR
Moving field service software is feasible but unforgiving of shortcuts. A staged plan lowers the risk: four days of preparation, about a week of rollout (the office, then one truck, then the fleet), and a few days of validation before you cancel the old plan. Compressing it into a weekend is how data gets lost, QuickBooks issues get missed and technicians lose confidence.
This playbook is a suggested plan, not a guarantee. It applies whichever platform you are leaving, because the data mapping, QuickBooks and customer-communication mechanics are common to all of them. Where it names IntelliDrive OS, it describes what the product does today, including its limits.
Before you start: what IntelliDrive OS imports
In Settings → Import & Export, IntelliDrive OS imports products, customers, suppliers, stock quantities by location, services, outlets, registers, payment types and past sales from CSV files. Each import has a downloadable template, a field-mapping step and a preview of the first five rows, and it finishes with a count of what was created, updated, skipped and failed. You can export the same data at any time.
It does not import scheduled jobs. Those live in the GetTimePad add-on ($199/month), so ask how your open jobs will move; see scheduling and dispatch. Decide how to handle open invoices too: many shops let existing ones finish in the old system and enter only new work in the new one.
Pre-migration: the four days that decide everything
Day -4: Audit the current state.
- Export your data from the current platform and count customers, active jobs, open invoices and recurring services
- List the custom fields you use heavily
- Check the QuickBooks connection: last successful sync and anything pending
Day -3: Set up the new platform.
- Create the account, enter your business details and set your tax rate (IntelliDrive OS uses one tax rate per shop location)
- Connect QuickBooks Online, but do not push anything yet
- Add your users, your locations (the shop and each van), your services and your product catalog
Day -2: Run a sample migration.
- Import a subset: about 50 customers and the products you sell most
- Check the field mapping, and decide where every custom field goes or whether to drop it
- Spot-check 10 random customers for accuracy
Day -1: Tell your customers and brief your team.
- Send a short email or text to active customers explaining what changes (a script is below)
- Give the office a written runbook for the migration sequence
- Pick the first technician for the field rollout
Customers who are told what is happening are less likely to be confused or to question a charge, so do not skip this step.
Days 1–3: the office moves first
The office team moves first, with the field still on the old platform. That keeps the migration risk inside a small, controllable group.
Day 1: Customers, products and stock.
- Import the full customer list, products and stock quantities from CSV
- Check the counts: customers in the old system should match customers in the new one, apart from known duplicates
- Spot-check 20 random customers and a sample of products
Day 2: Open work.
- Decide what to do with active jobs and open invoices, and apply the same rule to every one
- The office starts using the new system for new sales; the old platform stays available read-only for lookups
Day 3: QuickBooks.
- Before you connect, export your QuickBooks customer list with email and phone, so you can match rather than duplicate
- Decide who runs the IntelliDrive OS push to QuickBooks Online and when. It is a one-way push that you start, so give it an owner and a schedule
- Keep a reconciliation log for the first few weeks, noting each sale and payment and where it landed in QuickBooks
Days 4–9: field rollout, one truck then the fleet
The field migration is where most operations lose time. A staged rollout gives you a chance to find problems with one technician instead of all of them.
Day 4: The first technician.
- Pick your most adaptable technician, not the most resistant one; this is a learning sprint, not a stress test
- IntelliDrive OS runs in the browser on a phone or tablet and can be added to the home screen
- Give them a 30-minute walkthrough, then send them out to work live
- Hold a short debrief with the office at the end of the day
Days 5–7: The first technician works in the new system exclusively. Write down every workaround they find.
Day 8: Add two or three more trucks. By now the first technician can help train them, which usually works better than office-led training.
Days 9–10: Bring the whole fleet over. The office handles exceptions for the first two days.
Days 10–14: validation and decommission
Days 10–12: Parallel run and validation.
- Keep the old platform read-only for historical lookups
- Each day, check a sample of about 10 sales against QuickBooks
- Hold a short weekly retro with technicians to catch friction early
- Send yourself a test payment link and confirm the whole path works: link, signature and terms page, payment and receipt
Day 13: Phone numbers.
- If your current platform provides a business number, port it well before this point, not on the same day
- Test inbound calls with a real call from your cell phone
Day 14: Decommission the old platform.
- Cancel the old subscription only after a final full export of your historical data, stored offline
- Confirm no technician is still using the old app
QuickBooks: three things that go wrong
QuickBooks is where migrations most often leak data. Watch for three problems:
1. Duplicate customers. When you connect a new system, it may treat existing QuickBooks customers as new, leaving two records for each. Export your QuickBooks customer list first and match by email and phone.
2. Number continuity. If the new system numbers sales or invoices differently, you can end up with numbers that collide with your last ones. Check how numbering carries over before you push anything.
3. Classes, locations and ownership. If you use classes or locations in QuickBooks, test a few pushes and check how they land before you rely on them. Because the IntelliDrive OS push is one-way and starts when you run it, make sure one person owns it and runs it on a fixed schedule.
Whatever the platform, keep a reconciliation log for the first few weeks, so problems surface within days rather than at month-end.
The customer communication script
The customer-facing piece is easy to underrate. Two short messages are enough.
Day -1 email (subject: "A quick heads-up about our system this week"):
Hi [name], a quick heads-up: we are changing the system we use for sales, receipts and payment links this week. Your upcoming appointments will run as scheduled. From [date] your receipts and payment links will come from our new system, and the pages may look a little different. If you have any questions, reply here or call us at [number]. Thanks, [owner name].
Text with the first payment link from the new system:
Hi [name], this is [business]. Your payment link for [job] is below. It comes from our new system, so the page may look different. Reply if anything looks off.
Migration anti-patterns (what not to do)
These patterns consistently produce bad migrations:
1. A big-bang cutover. "We will switch everything Monday at 8 AM" concentrates all the risk into one window, where one problem cascades.
2. Skipping the sample migration. Going straight from a full export to a full import without testing field mapping on about 50 customers means mapping problems surface when there are thousands of records to fix.
3. Disconnecting QuickBooks without a plan. If the old platform is disconnected before every open item is reconciled, you get messy entries for weeks.
4. No customer communication. Customers find out about the change when something looks different, and some question the charge.
5. Migrating in peak season. Switch during your slow period if you can.
6. Decommissioning the old platform early. Keep it read-only for the whole plan. Historical lookups matter, and cancellation can wait.
7. Skipping the reconciliation log. Without a short daily check against QuickBooks, you find sync problems at month-end, when they are harder to untangle.
Next steps
If you are deciding whether to move at all, start with the seven triggers. If you have decided, start your free trial and run the sample migration on a real subset of your customers: the first 30 days are free, and a card is required at signup. See pricing for what the flat price covers.