Most accounting software switches fail not because the new tool is worse, but because the migration destroys more value than the license fee ever saved. You lose historical reports, break tax compliance trails, discover API limits mid-project, and hand-enter data for weeks while both systems run in parallel. By the time you're live on the new platform, you've burned 80 hours of labor and gained nothing. The trap is asking the wrong questions. Vendors will show you beautiful dashboards and promise seamless imports. What they won't tell you is that your cash reconciliation data doesn't export cleanly, or that your five years of tax classification detail vanishes, or that their API won't talk to your CRM for another three months while you manually sync client invoices. Before you evaluate a single feature, ask these 12 questions. They reveal the real cost of migration—and often prove that staying put is cheaper than moving. 1. Can you export every transaction with full tax classification history? This is the most expensive gotcha. Your new software needs to know not just that you invoiced Client X for $5,000, but that $3,000 was taxable service income, $1,200 was GST-exempt, and $800 was a deferred retainer. Most platforms export transactions, not classifications. Ask the vendor: Can I export GL account coding, tax category assignments, and custom fields in a single file? Will historical classifications carry over, or do I re-code everything? If I'm using multi-country tax rules (Malaysia SST, Indonesia PPN, Singapore GST), does the export preserve all three regimes? If the answer is "we'll help you set up a clean chart of accounts and you can map as you import," that's code for "you're recoding six months of transactions by hand." 2. How far back does your historical reporting go, and at what cost? Your accountant needs last year's P&L to file this year's taxes. Your auditor needs three years of GL detail. Your lender wants five years of cash flow. Ask: Can I query historical data (invoices, expenses, GL entries) from Year 1 without exporting the entire database? Is there a per-gigabyte charge for historical data retrieval, or is it included? If my old system dies, can I maintain read-only access for compliance, or do I lose it entirely? Some platforms charge you to keep old data alive on their servers. Others force you to export everything and maintain your own archive—which means you now own backup, security, and recovery responsibility. 3. When tax law changes (GST rate shift, new filing category), how quickly does your software update? Tax rules don't wait for software release cycles. Malaysia introduced MyInvois in 2024. Indonesia changed PPN rules mid-year in 2024. Singapore's IRAS requirements shift annually. The wrong answer: "We'll update in the next quarterly release." By then you've invoiced 200 clients under the old rule and your compliance is a mess. Ask: How many days between a tax authority announcement and when your platform applies the change automatically? Can you roll back historical invoices if a tax rule retroactively changes? Who bears the cost if my invoices don't comply with a new regulation and you updated late? If they can't answer within days—not weeks—and can't retroactively correct invoices, the risk is yours alone. 4. What are your API rate limits, and when do you charge for overages? You'll need to sync invoices to your CRM, pull data into reports, maybe trigger automations. The vendor's free tier might handle 100 API calls per day. Your business does 500. Ask: What's included in my plan: calls per day, per month, or per request? At what point do overages kick in, and what's the cost per 1,000 calls? Can I batch queries to stay under the limit, or are calls metered individually? If I hit the limit, does the API queue requests or return errors? The difference between "100 calls per day, overages $0.01 per call" and "500 calls per day included, overages $1 per call" is $1,000 per month on scaling. Lock this in before migration. 5. Which integrations are built-in, and which require a third-party connector like Zapier? A built-in integration to your CRM means data syncs instantly and reliably. A third-party connector (Zapier, Make, PapayaWhip) means you're dependent on a middleman's uptime, rate limits, and pricing. Ask: What CRMs, payment processors, and booking platforms have native integrations? For integrations not built-in, which third-party tools do you officially recommend and test? If a Zapier integration breaks, who debugs it: me, you, or Zapier? Are there per-action charges on third-party connectors that could scale beyond the software's own fee? If your CRM and accounting software don't integrate natively, you're building a Frankenstein system held together by Zapier automation—and you're paying Zapier every time a transaction syncs. 6. Can you handle multi-country invoicing with local tax compliance, or do you only support one region? If you invoice clients in Malaysia,