You've outgrown your accounting software. The new platform promises better reporting, tighter integrations, and fewer late-night reconciliation headaches. But before you commit, you need to know: what actually comes with you when you migrate?
When you switch accounting software, your core financial data transfers in most migrations: chart of accounts, transactions (invoices, bills, payments), customer and vendor records, and account balances. However, the completeness and accuracy of that transfer depends heavily on compatibility between platforms, your historical data quality, and whether you're using automated migration tools or manual export-import workflows. Attachments, custom fields, recurring transaction templates, and some audit trails often don't migrate cleanly—or at all.
Let's break down exactly what moves, what gets left behind, and what you need to plan for to avoid data loss or painful cleanup work after your switch.
Core Financial Data That Typically Transfers
The good news first: the accounting data that defines your business's financial position usually migrates successfully between modern platforms.
Chart of Accounts: Your entire account structure—assets, liabilities, equity, income, and expense accounts—typically transfers with account names, types, and numbers. Parent-child relationships in hierarchical charts of accounts usually preserve, though you may need to verify nesting after migration.
Historical Transactions: This is your financial history. Most migrations include:
- Customer invoices (paid and unpaid)
- Vendor bills and purchase orders
- Payment records and bank deposits
- Journal entries and adjustments
- Credit memos and refunds
The transaction history depth varies. Some businesses migrate 1-3 years of data; others need 7+ years for audit or tax purposes. More history means longer migration times and more opportunities for errors to compound.
Customer and Vendor Records: Contact databases transfer with names, addresses, payment terms, and outstanding balances. Customer payment history—who pays on time, who's chronically late—typically comes along as transaction records.
Account Balances: Your current receivables, payables, bank balances, and equity positions should match between systems on the migration cutover date. This is non-negotiable. If your accounts receivable shows $47,320 in the old system on June 30, it must show $47,320 in the new system as of the same date.
Tax Settings: Sales tax rates, tax groups, and tax tracking codes usually transfer, though you'll need to verify mappings. If your old system called it "CA Sales Tax" and the new one expects "California State 7.25%," that mapping needs manual attention.
Data That Often Transfers Incompletely
Here's where migrations get messy. These elements may partially transfer, transfer in unusable formats, or require manual reconstruction:
Attachments and Documents: That PDF invoice your vendor emailed? The receipt photo attached to an expense? Many accounting platforms store attachments differently. Some migrations lose them entirely; others preserve them but break the links to their parent transactions. Budget 10-20 hours to reattach critical documents if you have thousands of transaction attachments.
Custom Fields: If you added fields to track project codes, departments, or custom reporting dimensions, those rarely migrate automatically. The data may exist in your export file, but mapping it to custom fields in the new system often requires scripting or manual data manipulation.
Recurring Transaction Templates: Your monthly rent invoice template, your weekly payroll journal entry—these automation rules live in your old system's configuration, not your transaction history. You'll recreate these manually, which typically takes 2-4 hours depending on how many recurring items you've set up.
Bank Reconciliation History: Your bank feeds and reconciliation markers ("this transaction cleared on July 15") may not transfer. Many businesses restart bank reconciliation fresh in the new system, matching only unreconciled transactions and accepting prior months as reconciled in the old system.
Multi-Currency Data: If you operate in multiple currencies, historical exchange rates and realized/unrealized gain-loss calculations may not transfer accurately. This is especially problematic for businesses with open foreign-currency invoices spanning the migration date.
Class and Location Tracking: QuickBooks classes, Xero tracking categories, or custom segment reporting fields may have different structures in your new platform. The underlying data exists in your transactions, but reformatting it to match the new system's taxonomy requires thought and often manual mapping.
Data That Rarely Transfers
These elements almost never migrate automatically. Plan to rebuild them or accept their loss:
User Permissions and Roles: Your team's access levels, approval workflows, and role-based permissions are system configuration, not financial data. You'll set these up from scratch in the new platform.
Integrations and API Connections: Every Zapier workflow, every payment processor integration, every CRM sync—these die with the old system. Budget time to reconnect and test integrations after migration. For businesses with 5+ integrations, this often takes longer than the data migration itself.
Custom Reports and Dashboards: That margin-analysis report you spent three hours building? It doesn't export. You'll recreate it using the new system's reporting tools, which may be better or worse than what you had. Give yourself a week of casual use to rebuild your essential reports.
Audit Trails and Edit History: Some platforms track who changed what and when. Most migrations capture the final state of data, not the change log. If regulatory requirements mandate complete audit trails, you may need to retain read-only access to your old system.
Payroll History: Most businesses keep payroll in specialized systems (Gusto, ADP, Paychex) that don't migrate between accounting platforms. Your wage expense transactions transfer, but detailed payroll registers, tax forms, and employee setup rarely do. Payroll typically runs parallel during migration and isn't actually "migrated" in the technical sense.
Memorized Transactions and Templates: Beyond recurring transactions, many platforms let you save transaction templates ("repeat this invoice structure"). These don't transfer. Keep a list of your most-used templates and rebuild them in the first week.
What LedgerSwitch Actually Transfers
Traditional accounting migration meant exporting CSVs, formatting them in Excel for days, then importing and fixing errors for weeks. Modern migration tools automate the heavy lifting.
LedgerSwitch handles the complete data migration between major accounting platforms—chart of accounts, full transaction history, contacts, and balances—with field mapping and validation built in. Instead of manually reformatting thousands of rows in spreadsheets, you get automated data transformation with error checking before anything touches your new system. That means your team spends hours on migration, not weeks.
How to Verify Your Data Transferred Correctly
Never assume a migration worked. Always verify. Here's the minimum checklist:
- Balance Sheet Reconciliation: Run a balance sheet in both systems as of the migration cutover date. Every line item should match to the penny. If your old system shows total assets of $248,192 and your new system shows $248,150, you have a problem.
- Accounts Receivable Aging: Compare AR aging reports. Every customer balance and aging bucket (current,undefineddays,undefineddays, 90+ days) should match.
- Accounts Payable Aging: Same process for vendor balances and payment terms.
- Transaction Count by Type: Count your invoices, bills, and journal entries by month in both systems. If your old system hasundefinedinvoices in Q1undefinedand your new system shows 342, you have five missing transactions to find.
- Sales Tax Liability: If you collect sales tax, your tax liability reports must match exactly. Tax agencies don't accept "we lost some data in migration" as an excuse for discrepancies.
- Spot-Check Transactions: Randomly select 20-30 transactions across different types and dates. Open them in both systems and verify every field: amounts, dates, accounts, memos, customer names.
Budget a full day for verification with a complex data set (5+ years of history, multiple entities, inventory). Budget half a day for simpler books.
The Migration Timeline Reality
Most small business migrations take 2-4 weeks from decision to going live in the new system:
- Week 1: Data export, cleanup of obvious errors in source data (duplicate customers, unmapped accounts), initial mapping decisions
- Week 2: Test migration to a sandbox environment, verification, fixing mapping errors
- Week 3: Final data cleanup, second test migration, team training on new platform
- Week 4: Production migration, verification, parallel operation (running both systems for a week to catch issues)
Enterprise migrations with multiple entities, complex consolidations, or regulatory requirements can stretch to 8-12 weeks.
The mistake most businesses make: underestimating the data cleanup time. If your chart of accounts hasundefinedaccounts but you only actively use 80, your migration will carry overundefinedaccounts of baggage. Cleaning your data before migration makes everything faster and cleaner.
Frequently Asked Questions
How much transaction history should I migrate when switching accounting software?
Most businesses migrate 1-3 years of transaction history, which balances useful reporting with migration complexity. However, if you're in a regulated industry or anticipate audits, migrate at leastundefinedyears. You can always migrate summary balances for older periods and keep detailed transactions in the old system as read-only archives.
Can I migrate mid-year or should I wait until year-end?
You can migrate any time, but quarter-end dates are cleaner than mid-month. Migrating mid-year means your annual tax reports will span two systems, which complicates year-end closing. If it's already June and your year-end is December, migrate now rather than waiting—six months of dual systems is worse than one split tax year.
What happens to my bank feeds when I switch accounting software?
Bank feeds don't migrate. You'll disconnect feeds from your old system and reconnect them in the new platform. Unreconciled transactions should migrate as data, so you can complete reconciliation in the new system. Most businesses see a 1-2 week gap in bank feeds during the transition, which you'll reconcile manually using bank statements.
Will I lose my audit trail when migrating accounting data?
Most migrations preserve what transactions occurred and when, but not who made changes or the edit history. If your industry requires complete audit trails, you may need to maintain read-only access to your old system for compliance. The new system starts building its own audit trail from the migration date forward.
Do I need to run two accounting systems during migration?
Yes, for at least 1-2 weeks. Run transactions in your old system while testing the new one, then switch to entering everything in the new system. Keep the old system read-only for at least a quarter to reference historical data and verify nothing was missed.
Making Your Switch With Confidence
Accounting migration isn't risk-free, but it's far less risky than staying in a system that doesn't serve your business. The data that matters—your financial position, your customer balances, your transaction history—transfers successfully when you use proper tools and verification processes.
The businesses that struggle with migration are the ones who click "import" on day one without testing, or who assume their five-year-old chart of accounts will magically organize itself. The businesses that succeed are the ones who treat migration as a project: test environments, verification checklists, and staged cutover dates.
Your financial data is portable. The workflow habits and custom configurations you've built are not. Budget time to rebuild the latter, and you'll find that switching accounting software is far less painful than you feared.