Manaz Afzal Book a consultation

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.

Findings from the review
IDFindingEvidenceRisk if left
F1Open jobs, recurring visits and unpaid invoices have no single cutover listFour exports that do not agree on open job countsWork or an invoice is missed on the switch day
F2Deposits already held in Jobber would be easy to take to income again in XeroOpen deposits with no liability mapIncome is recognised twice
F3Quotes accepted on the switch day have no owner in the current planNo rule for "accepted after 17:00"A job is created in both systems, or in neither
F4Tags and custom fields in Jobber have no ServiceM8 destination yet38 tags in use, 11 with no proposed fieldHistory is technically moved but cannot be filtered
F5A one-way trial copy already drifted after two daysJob notes added in Jobber did not appear in the copyA hard cutover would start from a stale file

Approach

  1. Write the mapping book and the keys

    Every field, and the Jobber job id as the idempotency key.

  2. Run a one-way mirror

    ServiceM8 is a shadow until the switch gate is signed.

  3. Publish a daily difference list

    Counts, status, next visit and invoices, with an owner for each row.

  4. Pilot, then switch, with a rollback list

    The rest of the team moves only after two clean mornings.

Current state and future state

Switch design, current idea versus the parallel run

Current state

JobberLive system
One exportWeekend cutover
ServiceM8Opens after the switch
Drift and gapsFound later

Future state

JobberStill live
One-way mirrorPlus a daily difference list
Pilot groupThen the rest
Switch dayWith a rollback to Jobber

Parallel-run modules

JobberSource of truth until switchn8n mirrorOne-way, idempotentServiceM8Shadow, then liveDaily compareEvery differenceGatesPilot, then switch

How it is built

Module-level build
  1. Module AMapping book

    Clients, sites, jobs, recurring visits, tags, notes, attachments and invoices, field by field.

  2. Module BOne-way mirror

    Creates and updates in ServiceM8 from Jobber events, never the other way, until the switch gate is signed.

  3. Module CDaily compare

    A difference list for counts, job status, next visit and open invoice totals, with an owner for each row.

  4. Module DPilot group

    A written set of technicians moves first. The rest stay on Jobber until the gate is met.

  5. 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

Core field map, Jobber to ServiceM8
JobberServiceM8RuleEdge
Client, property, billing addressClient and siteA client with two properties becomes one client, two sitesShared billing contacts are not merged into one site
Job numberJob number custom + new ServiceM8 numberThe Jobber number is kept for searchNever reused as the ServiceM8 primary id
Scheduled window, assigned techsBooking window and assigned staffNames mapped to ServiceM8 staff records firstA missing staff map parks the job
Recurring job templateRecurring serviceNext visit dates must match before the pilot gateA skipped visit is listed, not invented
Deposit and invoice stateNoted, then handled in the ledger cutoverDeposits already held are not taken to income againSee the deposits write-up if that is in scope
Quotes accepted after 17:00 on switch dayCreated only in ServiceM8, logged on the difference listThe runbook names the owner of that hourA second job in Jobber is cancelled with a note

Worked exhibits

Daily compare, day 9 of the parallel run
Jobber open jobs312
ServiceM8 shadow jobs312same count
Status differences3named on the list
Next-visit mismatches1held for the morning
Invoices out of step0
DifferenceJobOwnerRule until switch
Status: Jobber completed, ServiceM8 still scheduledJ-19004OperationsUpdate the shadow, do not invent a visit
Note added in Jobber after 21:00, not yet mirroredJ-18871Nightly replayReplay before the morning brief
Tech reassigned in JobberJ-19120DispatcherThe staff map must include the new name, then replay
Gates and the switch-day clock
  1. Day 0-3Mirror live, differences expected

    Mapping fixes only. No pilot moves yet.

  2. 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.

  3. 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.

  4. First week afterWatch list, then the Jobber account is set to read-only

    A written decision, not an automatic close.

Exceptions and runbook

Exception runbook
CaseRuleWho actsRollback
Job booked on the switch day in the old systemCancel with a note in Jobber, create once in ServiceM8DispatcherIf invoicing has already started in Jobber, it stays there until paid
Deposit paid in Jobber, job not yet startedCarry the held amount into the ledger cutover, do not re-recognise itFinanceThe deposit list from the morning of the switch is the source
Quote accepted after the switchServiceM8 only, loggedSales adminA Jobber quote left open is closed with a pointer to the new job
Mirror creates a duplicateThe Jobber job id is the key; a second create is refusedOperationsDelete the extra ServiceM8 job if one was created before the key was in place

How to read the exhibits

  1. The day-9 figures are a worked parallel-run morning, not a promise about a named company.
  2. The gates are signed decisions, not automatic moves.
  3. The rollback drill is part of the test plan, not an afterthought.

Test plan

PASS / FAIL checks
IDCheckMethodPASS whenFAIL when
T1Count matchLoad a frozen Friday fileOpen job counts agreeAn unexplained gap
T2Idempotent mirrorReplay a day of eventsNo second ServiceM8 job for the same Jobber idDuplicates
T3Daily compareIntroduce a known status changeIt appears on the list the next morningIt is missed
T4Pilot gateTwo clean mornings, then one planted differenceThe gate stays closed until the difference is namedThe rest of the team is moved anyway
T5Switch-day quoteAccept a quote at 17:20 in a rehearsalOne ServiceM8 job, Jobber quote closed with a noteJobs in both systems
T6Rollback drillFire a rollback trigger in rehearsalNew work returns to Jobber inside the written timeStaff are left unsure which system to use

Scope

AreaIncluded
DiscoveryJobber setup, open work, deposits and invoice state, with written findings
Mapping bookClients, jobs, recurring work, tags, notes, attachments and invoices
One-way mirrorn8n flows with idempotent keys
Daily compareDifference list and owners
Pilot and switch runbookGates, clock, rollback triggers
Test planIncluding a rollback rehearsal
Handover and supportSOPs, walkthrough, 14 days of fixes, optional monthly hour block
Not includedThe ledger cutover itself, staff rostering, or a second job system after rollback is chosen

Rollout, handover and monthly support

MilestoneDeliverableTimingShare of fee
M1 Discovery and mappingFindings and the field book, signedWeek 120%
M2 Mirror and compareLive in a shadow, daily list runningWeeks 2 to 335%
M3 PilotPilot group on new jobs, gate met or exceptions namedWeek 4 to 530%
M4 Switch and handoverSwitch runbook, first-week watch, 14 days of fixesWeek 615%
Handover and monthly support

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.

Related work snippets

Next step

Bring me the work that repeats.

I scope it in writing, test it against your current process on your own data and hand over everything I build.

Book a consultation