Move the future bookings, balances and service details as carefully as the customer list. A contact import alone will not show whether recurring dates, staff assignments, prices and reminders survived the move.
Treat migration as a controlled operational change. The objective is one accurate source for future bookings and a clear boundary between old and new notifications and collection.
Separate four kinds of information
| Information | What needs to survive | What not to assume |
|---|---|---|
| Customers | Identity, contact route, service address and agreed instructions | Every field maps automatically |
| Future work | Dates, frequency, duration, assignments, extras and status | A customer import recreates a calendar |
| Financial records | Open invoices, payments, balances and required history | Historical data is editable or complete in the new product |
| Payment methods | A supported, authorized collection path | Stored cards are part of an ordinary CSV export |
Do not move raw card data through spreadsheets. Handle property-access instructions separately with appropriate permissions. Use fictional records for initial testing rather than giving an unapproved environment sensitive customer data.
Establish what the vendor will actually import
ZenMaid's June 2026 import documentation describes concierge onboarding, says appointment import requires a paying account and notes that manual bulk import is not currently available. BookingKoala's public documentation describes import tools and some processor-record matching. These are different capabilities, not a universal promise that every field or schedule can migrate unchanged. ZenMaid data import BookingKoala pricing
Get the available import scope and format for the account you are buying. Distinguish a paid migration service from included assistance, and a customer import from a future-appointment migration. Do not build the project around an assumed feature simply because a competitor's review says “easy migration.”
Pick a cutover boundary
Choose a clear service date or operational boundary. Work before the boundary remains owned by the old process unless intentionally migrated. Work after it belongs to the new one after reconciliation. Document how changes arriving during the transition will be handled.
Avoid an undefined overlap where one staff member edits the old calendar and another edits the new calendar. Maintain a temporary change register so reschedules and new bookings are applied consistently during the move.
The exact day is a business decision, not a universal weekend recommendation. Pick a period when someone can check the work and respond to exceptions.
Reconcile future visits, not just totals
A matching total count is necessary but insufficient. Two records may be wrong in opposite directions. Compare a unique customer/job reference, next date, recurrence rule, arrival window, duration, assigned people and price for each future job in scope.
Spot-check difficult cases: a first clean priced differently from later visits, a paused recurring customer, an alternating-week customer and a one-time add-on. A clean that occurs every four weeks should not silently become calendar-monthly.
Use the appointment counter to reason about expected occurrences. The actual vendor export remains the evidence of what the system holds.
Keep notifications and payments from firing twice
Before the new system sends production messages, identify every active reminder in the old one. Decide when it stops, then test the new sender with authorized recipients. The same customer should not receive two conflicting confirmation times.
For payments, identify scheduled charges and saved-method status. Do not leave both systems set to collect for the same future service. A migrated invoice does not automatically transfer the authority or technical ability to charge a stored method.
The payments guide separates these states. An authorized collection process is more important than a superficially complete import percentage.
Moving and reconciling accounting records
Connecting a new operations platform to the same QuickBooks file can introduce duplicate customers or invoices if historic and future records are handled inconsistently. Have the person responsible for the ledger approve the import and sync boundary.
Jobber's new integration and Housecall Pro's documented sync have specific directional and correction behavior. Do not connect first and plan reconciliation later. Jobber new QuickBooks Online sync Housecall Pro QuickBooks Online sync
Test a new invoice, partial payment, edited invoice and refund through the intended account version. Preserve the old records needed for reporting and compliance; this guide does not prescribe a universal retention period.
What to check before canceling the old account
The replacement should contain the agreed future schedule, staff should be able to use it, notifications should be correct, collection should be controlled, and necessary historic records should be accessible. Save the old account's usable exports and relevant subscription terms before ending access.
ZenMaid's pricing lists export functionality at Pro Max. That is a plan-feature question to settle before the move; it is not proof that lower-tier users have no legal rights to their information. ZenMaid pricing
A cancellation can be final even when an annual prepayment is not refunded. Read the actual order terms rather than assuming “cancel anytime” guarantees money back.
Keep a record of the move
Write a short record: what moved, what did not move, what remains in the old system, who checked future work and when customer messaging changed. Record unresolved exceptions explicitly rather than marking the project complete because the import screen finished.
Use the trial checklist before migrating and the cost guide to judge whether subscription savings still make sense after setup and disruption costs.
Download the migration reconciliation worksheet. Keep customer data in an appropriately controlled system.
Calculate the first-year decision
Use the switching and commitment calculator for setup cash, parallel running, time and recurring costs. It deliberately reports no payback when the assumed recurring saving is zero or negative. The notification event map records which old reminders must be suppressed during cutover.