TL;DR
A clean migration from a legacy ConnectWise-to-Xero sync to a current vendor takes four to six weeks elapsed, six to twelve hours of active MSP staff time. The 14-step checklist below covers inventory, mapping carry-over, parallel run, reconciliation, cut-over, and decommission. The hardest two steps are step 1 (inventory) and step 7 (reconciliation); everything else is mechanical.
Why migrations need a checklist
Most failed migrations between sync vendors fail because someone skipped a step that did not seem important at the time. The inventory step gets skipped when the bookkeeper assumes the new vendor will figure out the mappings on its own. The parallel-run step gets skipped when the MSP wants to "save a month" by cutting straight over. The reconciliation step gets compressed when the cut-over date is fixed and the variance is uncomfortable.
None of these shortcuts save time at the calendar level. They all defer the cost of the migration into the first three months of the new sync, where it shows up as month-end close anomalies that take longer to diagnose because no one remembers what the legacy sync was doing.
The 14-step checklist below is what we walk every customer through when they migrate to Connect Zero from another sync vendor. It is conservative; the active time is six to twelve hours total, which is cheap insurance against a six-week month-end-close mess.
Pre-migration phase (steps 1 to 5)
Step 1: Inventory current sync configuration (60 to 120 minutes). Open the legacy sync admin console. Document every mapping (agreement-to-revenue-account, product-to-revenue-account, tracking-category, expense routing, time-entry treatment), every override (tax code, account override, currency override), and every custom rule (inter-company billing, fixed-rate overrides, batch-window settings). The output is a single document or spreadsheet. Without it, the new sync inherits no defaults and the parallel-run will surface variance for reasons no one can explain.
Step 2: Snapshot Xero state (30 minutes). Export the current Xero invoice list (last 90 days), the agreement balances, the tracking-category state, and the chart of accounts. These are the reference state against which the parallel-run will be compared. Keep them in the MSP's finance archive for the audit trail.
Step 3: Map ConnectWise locations to Xero entities (30 to 60 minutes, multi-entity MSPs only). For MSPs running one Xero entity per legal jurisdiction or per region, document which ConnectWise locations route to which Xero entities. Sometimes the legacy sync has implicit routing rules that aren't visible in the admin console; check by sampling 5 to 10 invoices per entity. Per the multi-currency international MSP guide, the routing rules drive the FX accounting.
Step 4: Configure Connect Zero on a Xero test entity (15 to 30 minutes). Install Connect Zero from the Xero marketplace. OAuth to a Xero test organisation (Xero supports free demo organisations specifically for this purpose). OAuth to ConnectWise (same OAuth flow as the legacy sync uses). The point is to confirm both connections without touching live invoices yet.
Step 5: Apply mapping carry-over (60 to 120 minutes). Transcribe the inventory from step 1 into the Connect Zero admin. The shape is the same as the legacy sync (agreement-to-account, product-to-account, tracking-category, etc.); the names differ vendor by vendor. Where the legacy sync had a setting that Connect Zero exposes differently, decide which behaviour to keep; usually the legacy behaviour, unless there is a documented reason to change.
Parallel-run phase (steps 6 to 8)
Step 6: Run parallel sync for one month (one month elapsed, 30 to 60 minutes active). Keep the legacy sync writing to production Xero. Configure Connect Zero to write to the Xero test entity. Both pull from the same ConnectWise. After one month, you have two parallel datasets covering the same invoices.
Step 7: Reconcile parallel run (90 to 180 minutes). The reconciliation walks through every invoice from the parallel-run month line by line. Compare total revenue per Xero account, per tracking category, per customer. Aim for variance under AUD 200 per month for an MSP doing AUD 1 million to AUD 5 million in revenue. Material variance walks back to a mapping in step 5 that does not match the legacy behaviour. The fix is at the mapping level, not the data level.
Step 8: Re-run reconciliation if material variance (90 to 180 minutes, conditional). If step 7 surfaced material variance, fix the mappings and run a second parallel-run cycle. Most MSPs need one parallel-run cycle; complex multi-entity MSPs occasionally need two.
Cut-over phase (steps 9 to 12)
Step 9: Schedule cut-over date (30 minutes). First business day of a new calendar month is the conservative default. Communicate the date to the finance team, the bookkeeper, and the operations lead. Block 90 minutes on the cut-over day for the cut-over plus immediate verification.
Step 10: Cut over (60 to 120 minutes). On the cut-over morning, disable the legacy sync (do not delete it; disable it so it stops writing but the config is preserved for rollback). Point Connect Zero from the test Xero entity to the production Xero entity (re-pointing, no re-installation). Run the first production sync.
Step 11: Spot-check first day (60 minutes). Watch the first 10 to 20 invoices land in production Xero. Spot-check three at random to confirm the agreement, account, and tracking-category mappings flowed through correctly. Watch the first batch (if batch) or the first hour (if real-time) closely.
Step 12: Run first month-end close (90 to 180 minutes, end of month). Use Connect Zero output for the first close. Flag any anomalies; most MSPs find zero, occasionally one. Document what was anomalous, fix the mapping, accept the variance for the first month if it is bounded.
Decommission phase (steps 13 to 14)
Step 13: Decommission legacy sync (30 to 60 minutes). After the first clean month-end close, cancel the legacy sync subscription. Document the cancellation date for the records. Archive the inventory from step 1 in the MSP's finance archive for as long as record-retention policy requires.
Step 14: Document the new operating model (30 to 60 minutes). Update the MSP's finance SOP with Connect Zero as the data source. Re-train any bookkeeper or finance staff who used the legacy sync admin console. The Connect Zero admin is documented at the setup guide; most bookkeepers self-onboard in an afternoon.
Total time and what to expect
| Phase | Active time | Elapsed time |
|---|---|---|
| Pre-migration (steps 1 to 5) | 3.5 to 6.5 hours | 1 to 2 days |
| Parallel-run (steps 6 to 8) | 3 to 6 hours | 4 weeks |
| Cut-over (steps 9 to 12) | 4 to 8 hours | 3 weeks |
| Decommission (steps 13 to 14) | 1 to 2 hours | 1 week |
| Total | 11.5 to 22.5 hours | 9 to 10 weeks |
The elapsed time is dominated by the parallel-run wait (which is the cheap insurance) and the cut-over-to-decommission gap (which is the rollback window). The active time is dominated by step 1 (inventory) and step 7 (reconciliation), which is why those two steps deserve the most preparation.
Common pitfalls
- Skipping the inventory step. The new sync inherits no defaults. Every variance in the parallel-run is unexplained, which slows the reconciliation.
- Cutting over mid-month. The first close becomes fragmented (legacy for half, new for half), which adds complexity.
- Treating the parallel run as optional. Discovering mapping issues at the first month-end close is more expensive than discovering them during a parallel-run cycle.
- Deleting the legacy sync before the first clean close. Rollback becomes harder. Disable, do not delete, for 30 to 60 days.
- Underestimating the reconciliation step. Step 7 is the longest active-time step. Plan for it.
Frequently asked questions
How long does a ConnectWise Manage to Xero migration take?
Four to six weeks elapsed, dominated by the one-month parallel-run cycle. Six to twelve hours of active MSP staff time spread across the four weeks.
Can I cut over without a parallel run?
You can, but we would not. The parallel-run cycle is what makes the variance visible while you still have both syncs to compare. Without it, you discover mapping issues at the next month-end close.
What is the cut-over date convention?
First business day of a new calendar month is the conservative default. Mid-month cut-over works but produces a fragmented period (legacy for the first half, new for the second half), which adds complexity to the first close.
Related: the WiseSync to Connect Zero migration playbook covers the seven-step version of this checklist for MSPs specifically switching from WiseSync; the 2026 buyer's guide covers the broader vendor evaluation; the monthly reconciliation guide covers step 12's recurring version.
What a typical migration day looks like
For the operations lead running the migration, here is the day-by-day picture for a 12-person Australian MSP migrating from a legacy sync to Connect Zero across a six-week window starting 1 April 2026.
Week 1, Tuesday 1 April: kick-off. Block 4 hours on the operations lead's calendar. Pull the legacy sync admin exports (step 1, 90 minutes). Snapshot Xero (step 2, 30 minutes). Document multi-entity routing (step 3, 60 minutes). End-of-day deliverable is a folder in the MSP's finance archive labelled "Sync migration April 2026" with the four exports and a one-page summary of the routing rules.
Week 1, Wednesday 2 April: install. Sign up for Connect Zero on the AUD plan, install the Xero marketplace app against the Xero test entity, install the ConnectWise OAuth (step 4, 30 minutes). Transcribe the mappings from yesterday's exports into the Connect Zero admin (step 5, 90 minutes). End-of-day deliverable is a Connect Zero admin showing all mappings in place, with a sentinel sync test (one invoice) confirming the connection works.
Weeks 2 to 5, 3 April to 30 April: parallel run. Connect Zero syncs to the Xero test entity in the background. The legacy sync continues writing to production Xero. The operations lead checks in weekly (15 minutes) to confirm no failures on either side. End of week 5 deliverable is two parallel datasets covering one full calendar month.
Week 6, Monday 4 May: reconciliation. Block 4 hours. Run the per-customer comparison (step 7, 90 to 180 minutes). If clean variance under AUD 200, schedule cut-over for the following Monday. If material variance, fix mappings and queue a second parallel-run cycle (rare for typical MSPs; common for multi-entity).
Week 6, Monday 11 May: cut over. Block 4 hours. Disable the legacy sync (do not delete), re-point Connect Zero from test entity to production entity, run the first production sync (step 10, 60 to 120 minutes). Watch the first hour closely (step 11, 60 minutes). End-of-day deliverable is the first 10 to 20 invoices verified in production Xero.
Weeks 7 and 8, 12 May to 25 May: bedding-in. Daily check on the sync output. No active steps. End-of-period deliverable is two clean weeks of sync.
Week 9, end of May: first month-end close on Connect Zero (step 12, 90 to 180 minutes). The 30-day cycle covers part-legacy, part-new (the cut-over was mid-month). The first all-new close is at end of June.
Week 10, mid-June: decommission (step 13, 30 to 60 minutes) and SOP update (step 14, 30 to 60 minutes). Cancel the legacy sync subscription, archive the exports, update the finance SOP.
Multi-entity MSPs: do step 3 properly
For MSPs running more than one Xero entity (typical above AUD 5 million revenue, or any MSP with subsidiaries in multiple legal jurisdictions), step 3 is the make-or-break.
The pattern is one Connect Zero sync connection per Xero entity, each filtering on a different set of ConnectWise locations. The location-to-entity routing rules need to be documented before the install, because the sync admin needs to know which ConnectWise locations route where. If the routing rules are vague ("most Sydney customers go to the AU entity, except a few that go to the holding"), the parallel-run will surface mis-routing and the reconciliation step extends.
For Pattern B multi-currency MSPs (per the multi-currency guide), the entity-per-jurisdiction pattern doubles the time on steps 4 to 14 because each step runs per entity. A two-entity MSP runs the 14-step checklist twice; a three-entity MSP runs it three times. Plan the calendar accordingly.
The migration checklist is the on-ramp to a running ConnectWise to Xero billing flow. For the wider picture once you are live, see the complete ConnectWise to Xero billing guide for MSPs.
About this article
Written by the Connect Zero team, an Australian-built ConnectWise to Xero sync sold by Auswide IT, an Australian MSP integration vendor based in Adelaide. We have walked roughly 40 MSPs through this 14-step migration in 2026 Q1 and Q2. Last updated 24 May 2026.
