Migration Guide: How to Move from Workiz, Jobber, or Housecall Pro Without Losing Data

Migrating field service software is operationally feasible but unforgiving of shortcuts. The operations that complete clean migrations run a 14-day staged playbook: 4 days of pre-migration prep, 7 days of staged rollout (office → first truck → full fleet), and 3 days of validation + decommission. Operations that try to compress this into 3–5 days routinely lose data, miss QuickBooks reconciliation issues, and erode tech adoption.

This article is the operational playbook used by service businesses that migrated cleanly off Workiz, Jobber, or Housecall Pro to a flat-rate alternative. The playbook applies regardless of which specific platforms you are migrating between — the data integrity, QuickBooks reconnection, and customer communication mechanics are common across the category.

Day -4: Audit current state.

• Pull a CSV export from your current platform (Workiz/Jobber/HCP all support this from the admin dashboard)
• Count customers, active jobs, open invoices, scheduled recurring services
• Identify custom fields used heavily in the current setup
• Pull the QuickBooks integration status — last successful sync, any pending reconciliation

Day -3: Set up the target platform.

• Create the account, configure business info, tax settings, time zones
• Connect QuickBooks Online (or whatever accounting backend you use) — but DO NOT trigger initial customer sync yet
• Configure tech accounts (without sending invites yet)
• Set up service catalog: job types, parts categories, labor rates

Day -2: Run a sample migration.

• Export a subset: 50 customers + their last 5 jobs + open invoices
• Import to the new platform via CSV
• Validate field mapping — every custom field needs a destination field or a documented decision to drop it
• Spot-check 10 random customers for data integrity

Day -1: Customer communication + tech briefing.

• Send email + SMS to active customers: "We're upgrading our system on [date]. Your appointments will continue as scheduled. Here's the new portal link for self-service [URL]."
• Brief the office team on the migration sequence with a written runbook
• Schedule the first tech for mobile-app onboarding (1 tech on day 4, full fleet on day 10-12)

Per Service Council 2024 research, operations that skip the customer communication step report 12-18% lower customer retention through the migration. The pre-migration communication is not optional.

The office team migrates first, with the field still running on the old platform. This isolates migration risk to a controllable cohort.

Day 1 (Monday): Customer + service data migration.

• Full customer export from old platform → CSV import to new
• Validate count: customers in old = customers in new (within 2-3% for known-deduplication)
• Spot-check 20 random customers for field integrity
• Recurring services migrated separately — verify next-scheduled date

Day 2 (Tuesday): Active job + open invoice migration.

• Active jobs (scheduled but not completed) — migrate with full details + attached customer
• Open invoices — migrate with payment status preserved
• Office team starts using new platform for scheduling new jobs; old platform stays available read-only for historical lookup

Day 3 (Wednesday): QuickBooks reconnection.

• Disconnect old platform from QBO (this is the riskiest step — do it AFTER all open invoices are migrated)
• Connect new platform to QBO
• Run initial sync — expect duplicate customer warnings; resolve via email + phone matching
• Start a 21-day parallel reconciliation log (track every invoice + payment for the first 21 days to catch sync issues)

Per Intuit's documentation, customer GUIDs reset on reconnection — duplicate-prevention requires careful matching by email + phone. Plan 4-8 hours of office time on day 3 for the QBO reconnection.

The field migration is where most operations lose time. Staged rollout has 3.2x higher tech adoption per Service Council research; big-bang rollouts have predictable failure modes.

Day 4 (Thursday): First tech on the new mobile app.

• Pick your most-adaptable tech (not the most resistant — this is a learning sprint, not a stress test)
• Install new mobile app on their device
• Run them through 30 minutes of in-app demo
• Send them on their day with the new app for live work
• Office + tech share a quick debrief at end of day

Day 5-7: First tech operates on new platform exclusively. Catch the field UX issues before scaling. Document every workaround they identify.

Day 8 (Monday week 2): Add 2-3 more trucks. Same onboarding process. By now the first tech can help train the new techs (peer onboarding is materially more effective than office-driven training).

Day 9-10: Full fleet onboarded. Every tech on the new app. Office team handles exceptions for the first 48 hours.

Day 10-12: Parallel-run + validation.

• Old platform stays available read-only for historical lookup
• Daily QuickBooks reconciliation check (sample 10 random invoices for sync integrity)
• Weekly tech retro (15 min, end of each tech's day) — capture friction points
• Customer portal validation — ensure customers can log in and see their history

Day 13: Phone number cutover.

• If your current platform provides a phone number, port it 7-14 days before this point (not same-day)
• Validate inbound calls route correctly
• Test AI receptionist (if applicable) with a real call from your cell phone

Day 14: Decommission old platform.

• Cancel old platform subscription
• Final data archive — full export of all historical data, stored offline (compliance + dispute-resolution backup)
• Confirm no team member still has the old app on their phone

QuickBooks is where most migrations leak data. Three specific issues to watch:

1. Customer GUID reset. When you disconnect old platform and connect new, customer GUIDs reset. The new platform creates "new" customer records for existing QBO customers. Without deduplication by email + phone, you end up with two customer records for every active customer.

Mitigation: Before connecting the new platform, export a CSV of all QBO customers with email + phone. Use this as the deduplication source-of-truth.

2. Invoice number continuity. Some platforms reset the invoice number sequence on reconnection. If your sequence was 4731 and the new platform starts at 1000, you have invoice number collision.

Mitigation: Configure the new platform's invoice number to start above your highest current invoice number (4732 in this example).

3. Class / location mapping. If you use QBO classes or locations for P&L splits, the new platform needs to map jobs to the correct class. This mapping does not transfer in the CSV migration — it has to be reconfigured.

Mitigation: Document your current class/location mapping before disconnecting. Reconfigure in the new platform on day 3.

Per Intuit's published integration partner standards, real-time bidirectional sync requires specific webhook patterns and idempotency guarantees — different platforms implement these differently. Run a 21-day parallel reconciliation log to catch edge cases.

The customer-facing piece is undervalued. A clean migration with poor customer communication still produces churn. The script that works:

Day -1 email (subject: "We're upgrading our system this week"):

Hi [name], Quick heads up: we're upgrading our scheduling and customer system this week. Your upcoming appointments will run as scheduled. Starting [date], your customer portal will live at [new URL] — same login as before. If you have any questions, reply here or call us at [number]. Thanks, [owner name].

Day 0 SMS (when first customer logs into the new portal):

Hi [name], the new portal is live at [URL]. Your appointment on [date] is confirmed. Reply HELP if you need anything.

Day 7 follow-up email (only to customers who haven't yet used the new portal):

Hi [name], just confirming the new customer portal is live: [URL]. You can view your appointment history, pay invoices, and request service from the new system. Reply if you run into any issues.

Per Salesforce 2024 State of Service report, proactive customer communication during platform changes reduces churn by 8-14% vs no communication at all.

Operator: Mixed plumbing + drain operation, 9 trucks, Pacific Northwest, anonymized. Migrated from Jobber Grow to a flat-rate alternative in late 2025.

Pre-migration state: 9 paid Jobber seats, $249/month. 4,200 customers, ~180 active invoices, ~85 monthly recurring services, QuickBooks Online sync with 14 weeks of accumulated reconciliation backlog.

Migration execution:

• Day -4 to -1: Standard pre-migration prep. 8 hours of office time across 4 days.
• Day 1-3: Office migration. Caught 31 duplicate customer warnings on QBO reconnection. Reconciled cleanly within 6 hours of office work.
• Day 4-7: First tech (most-adaptable senior plumber) on new mobile app. Reported 3 minor UX friction points (job-completion flow needed an extra tap; photo capture was actually faster). Adopted cleanly.
• Day 8-10: Full fleet onboarded. One tech (least-adaptable) required an extra hour of one-on-one onboarding; resistant for 3 days then adopted.
• Day 11-14: Parallel-run validation. Caught 4 invoice sync delays in the first 7 days; resolved via support ticket. Day 14: decommissioned Jobber.

Outcome:

• Total migration duration: 14 days as planned
• Data integrity: 100% customer carryover; 4 historical jobs missing details (5+ year old records with corrupted custom fields); acceptable.
• Customer churn during migration: 0 reported issues; 3 customers asked for portal URL clarification, all resolved by SMS.
• Tech adoption: 8 of 9 techs adopted within 5 days; 1 tech took 9 days.
• QuickBooks reconciliation: 21-day parallel log caught 7 minor sync issues, all resolved without journal entries.
• Software cost: $79/month vs prior $249 (–68%)

Net assessment from the owner: "The 14-day playbook felt slow at day 3 when we were still on day-1 office work. By day 10 it was clearly the right pace. Everyone who tried to compress migration into 5 days at industry conferences I attended later had issues we didn't have."

Patterns that consistently produce bad migrations:

1. Big-bang cutover. "We'll switch everything Monday morning at 8am." This concentrates risk into a single window where one issue causes a cascade. Staged rollouts have 3.2x higher tech adoption per Service Council research.

2. Skipping the sample migration. Going straight from full export to full import without testing field mapping on a 50-customer subset. Mapping issues found at 4,000 customers are 80x more expensive to fix than at 50.

3. Disconnecting QuickBooks without an outflow plan. Old platform disconnected before all invoices are reconciled = double-entry chaos in QBO for 30 days.

4. No customer communication. Customers find out about the new portal when their old login fails. This is the largest single source of avoidable churn.

5. Migrating during peak season. July HVAC migrations and November Christmas-light-installer migrations fail at 2-3x the rate of off-season migrations. Time the switch for your operational slow period.

6. Decommissioning the old platform on day 3. Keep it read-only for the full 14 days. Historical lookup matters and decommission can wait.

7. Skipping the parallel reconciliation log. Without daily QBO sync checking for the first 21 days, you find sync issues at month-end when the cost-to-fix has compounded.

The operators who run clean migrations are the ones who treat it like an operational project, not a software install. The 14-day playbook isn't conservatism — it's the time the data integrity, QuickBooks reconciliation, customer communication, and tech adoption actually need. Compress it and you pay for it in churn, reconciliation errors, and tech friction for months after.

— Field service operations consultant, 19 years industry experience (anonymized)

Per Service Council 2024 Field Service Operations Research, staged platform rollouts have 3.2x higher tech adoption than big-bang switches. Per Salesforce 2024 State of Service report, the median platform migration recovers its switching cost inside 6 months when staged rollouts are followed.

If you have decided to switch (3+ triggers from the 7 triggers list) and want to see what a flat-rate destination platform looks like with the data migration walkthrough, book a 20-minute demo. The team can show you the sample migration on your real customer subset before you commit. The pricing page lays out the $79/mo flat-rate offer.