How to Switch Bookkeeping Services Without Breaking Your Books: A 30-Day Playbook
Founders put off switching bookkeepers for one reason: they're afraid of breaking something during the handoff. Lost transactions. Missed reconciliations. A tax season complicated by incomplete data. A month of confused reporting while the new team learns the chart of accounts. For many founders, the fear is big enough that they stay with a service that isn't working, month after month, because the idea of migration is worse.
It shouldn't be. Bookkeeping migrations are routine work for any decent service, and a well-run switch takes 3 to 4 weeks start to finish with no data loss and no disruption to closes. Most of the fear is based on imagined worst cases that rarely materialize when you run the migration properly.
This guide walks through the concrete 30-day playbook. Who does what, what needs to happen in what order, and how to avoid the common snags.
When to Start the Switch (and When Not to)
Best timing: month-end, ideally quarter-end. The scope of work to transfer is smaller and cleaner. Avoid switching mid-close or in the last 30 days before year-end (which gets complicated by tax prep).
Don't switch during an active fundraising diligence or right before an audit. Those need your financials to be in-motion and stable; a migration adds risk at the worst possible moment. If you're at one of those moments, delay the switch by 30 to 60 days until the event is behind you.
If you're clearly past the point where your current service is working (see our signs you've outgrown your bookkeeper piece), don't let fear of migration keep you static for another 3 months. The drift during those 3 months costs more than a clean migration does.
The 30-Day Playbook
Week 1: Evaluation and Selection
Day 1-3: Define what you want. Write down the specific problems you're solving for. Slow close? Unreliable reporting? High cost? Lack of SaaS depth? This becomes your evaluation criteria.
Day 4-7: Evaluate alternatives. Book discovery calls with 2 to 3 services that fit your profile. Ask each:
- Median close time at your stage
- Who's on your account and their roles
- Sample monthly deliverable
- How they handle deferred revenue
- Pricing and what's included
- Integrations supported
- Client retention rate
Same questions to each service. Compare side-by-side. Pick the service whose answers beat your current one on the dimensions that matter to you.
End of Week 1: Decision made. Verbal commitment to new service; contract review in flight.
Week 2: Contracts and Data Request
Day 8-10: Sign new service contract. Confirm start date (first day of the upcoming month is typical).
Day 10: Give notice to current service. Most services have a 30-day notice requirement. If you're switching on June 1, give notice by May 1 or ensure your contract allows shorter notice.
Tone matters here. A professional, non-combative exit makes the handoff smoother. Something like:
Hi [Current bookkeeper], after careful evaluation we've decided to transition our bookkeeping to [new service] effective [date]. We want to make the handoff as smooth as possible. Can we schedule a 30-minute call to walk through your current process and open items so we can ensure clean continuity?
Don't get into grievances. You're not trying to make a point; you're trying to get clean data.
Day 11-14: Request full data export. Specifically:
- Full QuickBooks (or Xero) file or equivalent export. Access credentials, admin rights, or a backup file.
- Trial balance as of the cutoff date
- 12 months of monthly P&L and balance sheets
- All supporting schedules: deferred revenue, fixed assets, prepaid expenses, accrued liabilities, stock compensation
- Reconciliation reports for every bank, credit card, and payment processor account
- Open items list: any uncategorized transactions, unresolved reconciliations, pending journal entries
- Accounting policy memo: the service's documented approach to your revenue recognition, expense categorization, and accrual treatments
If any of these are missing or delayed, that's a data-quality issue worth understanding. A well-run service has all of this organized and ready.
End of Week 2: Contracts signed. Notice given. Data request submitted.
Week 3: Onboarding and Parallel Setup
Day 15-18: Kickoff with new service. They'll need:
- Access to your accounting platform (or you'll transfer the file if moving platforms)
- Access to bank feeds, Stripe, payment processor credentials
- Access to payroll (Gusto, Rippling, etc.)
- Any bill pay systems (Bill.com, Ramp, Brex)
- Your HRIS (for employee data) if relevant
- Chart of accounts preferences
- Any custom report templates or preferences
The new service will also walk through the data received from the prior service. Quality issues (unreconciled accounts, ambiguous transactions, missing supporting schedules) get flagged here.
Day 18-21: Review and clean-up of historical data. The new service will produce a punch list of any issues in the handed-off data. Common items:
- Uncategorized or suspiciously-categorized transactions
- Balance sheet accounts that don't tie to supporting schedules
- Stock compensation expense missing or partial
- Deferred revenue that doesn't tie to contract schedules
- Accruals that should have been reversed but weren't
Address these before the cutoff date. If the clean-up is significant (6+ months of messy books), most services offer a catch-up or cleanup project before ongoing service starts. Budget $2K to $15K for cleanup depending on scope and complexity.
Day 21-24: Run a parallel close. If the cutoff is at month-end, the new service shadow-closes the current month alongside the outgoing service. This confirms the new team can produce consistent results with your actual data.
End of Week 3: Data clean, integrations connected, parallel close completed successfully.
Week 4: Cutover and First Full Close
Day 25-27: Official cutover. The new service takes over as primary. The old service completes any final responsibilities (typically: closing the prior month and confirming clean handoff).
Day 28-30: First full close under new service. This is the real test. The first full close should land on the service's target timeline (5 days at Median, 10 to 15 at more traditional services). If it slips significantly, surface it with the new team immediately; early close drift signals capacity problems.
End of Week 4: First clean close under new service. Migration complete.
Common Migration Pitfalls
Pitfall 1: Waiting for "perfect" data before switching
Some founders get stuck in diligence mode: "we need to clean up every open item before we can switch." This is backwards. Most cleanup is easier at the new service than at the old one. Hand off what you have, let the new team help clean up, and move forward.
Pitfall 2: Delaying the notice to avoid conflict
Some founders tell the new service they're signed but delay notice to the old one for weeks. This creates awkward double-billing and confusion. Give notice as soon as the new contract is signed.
Pitfall 3: Not requesting supporting schedules
The P&L and balance sheet are the obvious outputs. The supporting schedules (deferred revenue roll-forward, fixed asset roll-forward, prepaid amortization) are the work behind those numbers. Without them, the new service rebuilds from scratch, which takes weeks. Always request these specifically.
Pitfall 4: Migrating mid-quarter without calendar awareness
Mid-quarter switches are fine if your tax prep and external reporting calendars are clean. But don't migrate in Q1 if you're in the middle of a K-1 delivery, or in March if you're finalizing your Delaware franchise tax. See our tax calendar guide for the full set of deadlines to work around.
Pitfall 5: Skipping the parallel close
The parallel close feels like unnecessary work but it's the single best way to validate the new service can handle your data. Skipping it means the first real close is when you find out whether the new team can actually deliver. If there's a capacity issue, you'd rather discover it during a parallel than during a real close.
Pitfall 6: Underestimating cleanup scope
If your prior service was struggling (why you're switching), expect to find drift: uncategorized transactions, unreconciled accounts, missing schedules. Budget for cleanup up front. See our hidden cost of ignored books for context on what cleanup typically involves.
Key People and Their Roles
You (founder/CEO): Approve the selection, sign contracts, give notice, approve any cleanup scope. Don't try to do the migration work yourself; that's the service's job.
Your new service: Owns the migration plan, leads onboarding, identifies cleanup needs, runs the parallel close, delivers the first real close. A good service takes ownership of the migration and doesn't ask you to project-manage it.
Your prior service: Delivers the export, answers questions about their approach, transfers access credentials. A professional exit helps both sides.
Your tax partner: If bookkeeping and tax are separate, loop in your tax partner early. They need to know who to ask for data at year-end.
Your CFO or controller (if you have one): Review the handoff plan, sanity-check cleanup scope, validate the first close.
Your CTO or engineering lead: Only involved if there are custom integrations (unusual APIs, internal tools, custom billing). Usually not needed.
Cost of Migration
Three cost buckets:
New service onboarding fee: Usually $0 to $500 for standard onboarding. Some services charge a one-time fee; many waive it as a sales gesture.
Cleanup project (if needed): $2K to $15K depending on scope. A clean handoff from a well-run prior service has minimal cleanup. A messy handoff from a struggling service can involve several weeks of work.
Overlap billing: If the migration spans a month where both services charge you, expect to pay both for 2 to 4 weeks. This is unavoidable and should be factored into your decision.
Typical all-in cost of a clean migration: $1,000 to $5,000. A migration with significant cleanup can run $15,000 or more. Weighed against months of poor bookkeeping, even the higher end pays for itself quickly.
What Could Go Wrong (and How to Handle It)
The prior service delays or withholds data. Uncommon but it happens. Escalate to the firm's leadership and, if necessary, check your contract for data portability clauses. You have the right to your own financial data regardless of the service provider.
The new service underestimates cleanup. Ask for a written cleanup scope before committing. If the scope expands significantly during the work, renegotiate. Don't just accept the overrun.
The first close under the new service slips. Raise it immediately. Is it capacity? Unclear data from the handoff? Missing integrations? The response should be specific and measurable. If the service is defensive or vague, that's a bad signal.
You find material errors in the prior books after cutover. Common, unfortunately. Prior-period errors that were missed surface during the transition. These need to be corrected in the closed periods, which may involve amended returns or restatements. Work with the new service and your tax partner to document and correct.
You miss a tax filing deadline during the transition. If the migration disrupted tax prep, file extensions immediately. The penalty for a late-filed extension is far smaller than a late-filed return. Then recover with your new service and tax partner.
Frequently Asked Questions
How long does a bookkeeping migration really take? Well-run migrations: 3 to 4 weeks. Migrations involving significant cleanup: 6 to 8 weeks. If a service claims 1 week, they're either skipping steps or not being realistic.
Can I migrate without the old service's cooperation? Yes, though it's harder. You own your data. If you're on QuickBooks, you can extract the file yourself with admin access. If you're on a proprietary platform (like Bench), data portability is messier and you may have to rebuild some history. Plan accordingly.
Should I run books in both systems for a few months just to be safe? No. Parallel close for one month is enough. Running two full services indefinitely is expensive and creates confusion about which numbers are real.
What if I'm in the middle of a tax year? Mid-year migrations are common. The new service takes over starting from the cutover date; historical tax work for the year-to-date remains with the original service or is handed to your tax partner separately. Year-end filings are typically prepared by the service or tax partner who handles the full year.
Do I need to tell investors I'm switching? Usually no. Bookkeeping service changes are operational decisions that don't require investor notice. If diligence is active or imminent, a brief heads-up is appropriate. Otherwise, keep the switch internal.
What if I regret the decision after 3 months? The same migration playbook applies. Switching back isn't free but it's feasible. That said, if you picked carefully (asked the 8 evaluation questions, compared real alternatives), the odds of needing to switch back are low. Most regret comes from switching to a service that was also wrong, not from switching at all.
The Bottom Line
Switching bookkeeping services is a 30-day project, not a crisis. The playbook is well-worn: evaluate and select, give notice and request data, onboard and clean up, run a parallel close, cut over. A clean migration costs $1K to $5K in hard costs, plus a few hours of your time. The downside of staying with a service that isn't working is much larger: missed investor opportunities, tax mistakes, decisions made on bad data, and months of operational drag.
This week: If you've decided to switch, map out your 30-day plan. Identify your target cutover date. Book discovery calls with alternatives.
Next week: Sign the new service, give notice, start the data handoff.
Over the next month: Execute the playbook. The transition is routine when run properly.
If you're considering switching to a modern SaaS-native service, see how Median handles onboarding for startup founders migrating from Pilot, QuickBooks Live, Bench, or Kruze. A clean handoff and a 5-day first close should be the expectation, not the exception.