Work snippet
Jobber to ServiceM8 switch with a two-week parallel run
Concept DesignIllustrative integration walkthrough. Business details, figures and records are worked examples.
Moving fourteen HVAC technicians off Jobber and onto ServiceM8 without a gap. For two weeks a one-way mirror keeps the new system current, a daily diff lists anything that disagrees, and sign-offs at set points decide when the pilot crew moves and when ServiceM8 becomes the system of record.
The problemSwitching job systems risks losing jobs, customers and history mid-flight.
What changesA two-week parallel run with daily differences and signed gates for the switch.
- Area
- Job-system cutover
- Tools
- Jobber · ServiceM8 · n8n
- Typical scope
- US$2,500-4,200
- Timeline
- About 6 weeks · fixed milestones
The problem
Cutting over on a weekend from a single export tends to strand open jobs, deposits and quotes, and drift is only noticed after invoices are coming from both systems.
- Open job counts do not agree between exports
- Deposits already held can be taken to income again
- Quotes accepted on the switch day have no written owner
- A trial copy drifts within days because notes do not flow
What discovery would examine
A review of Jobber, QuickBooks Online, the planned ServiceM8 and Xero setup, and a week of jobs for a 14-tech HVAC business that wants to switch without a gap in invoicing.
| ID | Finding | Evidence | Risk if left |
|---|---|---|---|
| F1 | Open jobs, recurring visits and unpaid invoices have no single cutover list | Four exports that do not agree on open job counts | Work or an invoice is missed on the switch day |
| F2 | Deposits already held in Jobber would be easy to take to income again in Xero | Open deposits with no liability map | Income is recognised twice |
| F3 | Quotes accepted on the switch day have no owner in the current plan | No rule for "accepted after 17:00" | A job is created in both systems, or in neither |
| F4 | Tags and custom fields in Jobber have no ServiceM8 destination yet | 38 tags in use, 11 with no proposed field | History is technically moved but cannot be filtered |
| F5 | A one-way trial copy already drifted after two days | Job notes added in Jobber did not appear in the copy | A hard cutover would start from a stale file |
Approach
- Write the mapping book and the keys
Every field, and the Jobber job id as the idempotency key.
- Run a one-way mirror
ServiceM8 is a shadow until the switch gate is signed.
- Publish a daily difference list
Counts, status, next visit and invoices, with an owner for each row.
- Pilot, then switch, with a rollback list
The rest of the team moves only after two clean mornings.
Current state and future state
Current state
Future state
Parallel-run modules
How it is built
- Module AMapping book
Clients, sites, jobs, recurring visits, tags, notes, attachments and invoices, field by field.
- Module BOne-way mirror
Creates and updates in ServiceM8 from Jobber events, never the other way, until the switch gate is signed.
- Module CDaily compare
A difference list for counts, job status, next visit and open invoice totals, with an owner for each row.
- Module DPilot group
A written set of technicians moves first. The rest stay on Jobber until the gate is met.
- Module ESwitch and rollback
A timed runbook, a last difference list of zero or of named exceptions, and a trigger list that returns ownership to Jobber.
Field mapping
| Jobber | ServiceM8 | Rule | Edge |
|---|---|---|---|
| Client, property, billing address | Client and site | A client with two properties becomes one client, two sites | Shared billing contacts are not merged into one site |
| Job number | Job number custom + new ServiceM8 number | The Jobber number is kept for search | Never reused as the ServiceM8 primary id |
| Scheduled window, assigned techs | Booking window and assigned staff | Names mapped to ServiceM8 staff records first | A missing staff map parks the job |
| Recurring job template | Recurring service | Next visit dates must match before the pilot gate | A skipped visit is listed, not invented |
| Deposit and invoice state | Noted, then handled in the ledger cutover | Deposits already held are not taken to income again | See the deposits write-up if that is in scope |
| Quotes accepted after 17:00 on switch day | Created only in ServiceM8, logged on the difference list | The runbook names the owner of that hour | A second job in Jobber is cancelled with a note |
Worked exhibits
| Difference | Job | Owner | Rule until switch |
|---|---|---|---|
| Status: Jobber completed, ServiceM8 still scheduled | J-19004 | Operations | Update the shadow, do not invent a visit |
| Note added in Jobber after 21:00, not yet mirrored | J-18871 | Nightly replay | Replay before the morning brief |
| Tech reassigned in Jobber | J-19120 | Dispatcher | The staff map must include the new name, then replay |
- Day 0-3Mirror live, differences expected
Mapping fixes only. No pilot moves yet.
- Day 4-10Pilot group on ServiceM8 for new jobs, history still mirrored
Gate: the daily list has only named, accepted exceptions for two mornings in a row.
- Switch morningLast compare, then new work is created only in ServiceM8
Rollback trigger: more than five unexplained differences, or invoicing stopped for more than one hour.
- First week afterWatch list, then the Jobber account is set to read-only
A written decision, not an automatic close.
Exceptions and runbook
| Case | Rule | Who acts | Rollback |
|---|---|---|---|
| Job booked on the switch day in the old system | Cancel with a note in Jobber, create once in ServiceM8 | Dispatcher | If invoicing has already started in Jobber, it stays there until paid |
| Deposit paid in Jobber, job not yet started | Carry the held amount into the ledger cutover, do not re-recognise it | Finance | The deposit list from the morning of the switch is the source |
| Quote accepted after the switch | ServiceM8 only, logged | Sales admin | A Jobber quote left open is closed with a pointer to the new job |
| Mirror creates a duplicate | The Jobber job id is the key; a second create is refused | Operations | Delete the extra ServiceM8 job if one was created before the key was in place |
How to read the exhibits
- The day-9 figures are a worked parallel-run morning, not a promise about a named company.
- The gates are signed decisions, not automatic moves.
- The rollback drill is part of the test plan, not an afterthought.
Test plan
| ID | Check | Method | PASS when | FAIL when |
|---|---|---|---|---|
| T1 | Count match | Load a frozen Friday file | Open job counts agree | An unexplained gap |
| T2 | Idempotent mirror | Replay a day of events | No second ServiceM8 job for the same Jobber id | Duplicates |
| T3 | Daily compare | Introduce a known status change | It appears on the list the next morning | It is missed |
| T4 | Pilot gate | Two clean mornings, then one planted difference | The gate stays closed until the difference is named | The rest of the team is moved anyway |
| T5 | Switch-day quote | Accept a quote at 17:20 in a rehearsal | One ServiceM8 job, Jobber quote closed with a note | Jobs in both systems |
| T6 | Rollback drill | Fire a rollback trigger in rehearsal | New work returns to Jobber inside the written time | Staff are left unsure which system to use |
Scope
| Area | Included |
|---|---|
| Discovery | Jobber setup, open work, deposits and invoice state, with written findings |
| Mapping book | Clients, jobs, recurring work, tags, notes, attachments and invoices |
| One-way mirror | n8n flows with idempotent keys |
| Daily compare | Difference list and owners |
| Pilot and switch runbook | Gates, clock, rollback triggers |
| Test plan | Including a rollback rehearsal |
| Handover and support | SOPs, walkthrough, 14 days of fixes, optional monthly hour block |
| Not included | The ledger cutover itself, staff rostering, or a second job system after rollback is chosen |
Rollout, handover and monthly support
| Milestone | Deliverable | Timing | Share of fee |
|---|---|---|---|
| M1 Discovery and mapping | Findings and the field book, signed | Week 1 | 20% |
| M2 Mirror and compare | Live in a shadow, daily list running | Weeks 2 to 3 | 35% |
| M3 Pilot | Pilot group on new jobs, gate met or exceptions named | Week 4 to 5 | 30% |
| M4 Switch and handover | Switch runbook, first-week watch, 14 days of fixes | Week 6 | 15% |
Handover
- Written operating procedures for the happy path and each exception in the runbook
- A recorded walkthrough of the architecture, the queue and how to replay an item
- A credentials and ownership list, with every connection in your name
- Fourteen days of fixes after go-live, for defects in the agreed scope
Monthly support
A set block of hours each month, at US$35 per hour, agreed in writing before it starts. Typical use of the block: the first-week watch list, any late Jobber edits, and the decision to set Jobber to read-only
- Review of the exception queue and the weekly digest
- Small mapping or rule changes, agreed before they are made
- A short written note on what was done and what is still open
Typical scope for this kind of project: US$2,500-4,200
About 6 weeks · fixed milestones. The systems health check (US$150, fixed) comes first and confirms the scope. Extra hourly work is US$35 per hour, agreed before it starts. After handover, a set block of hours each month is available at the same rate, agreed in writing, to watch the flows, handle changes and work the exception queue.
Discuss an engagement.
Outline the operational problem through the contact form. I respond with a recommended starting point, including whether the US$150 systems health check is the appropriate first step.