Switching sales tax platforms does not reset your compliance history. It just changes where your records live — if the migration is done correctly. Most platform switches focus on go-live. The harder problem is what happens to everything before day one.
What You'll Learn
- Why platform switches create compliance gaps that are easy to miss
- What data needs to migrate before you go live on a new system
- The exemption certificate problem most migration plans skip
- What questions to ask any new vendor before signing
- How ACTSOLV is built for the B2B compliance use case
The key risk
If a state auditor initiates an audit covering the past three years, and your records for the first two of those years live in a system you no longer have access to, you have a documentation problem that no new platform can solve retroactively.
Most Platform Switches Create a Gap Nobody Plans For
The decision to switch platforms is usually driven by cost, missing functionality, or dissatisfaction with support. The evaluation focuses on what the new platform can do. What gets underplanned is the transition itself. A new system going live does not mean historical compliance data transferred cleanly. It often means historical data transferred in a format that is retrievable only within the old system — which you are no longer using.
Auditors don't care which platform you used. A state audit covers the full lookback period regardless of what system generated your records. The auditor cares whether the records exist and whether they support the tax treatment applied to each transaction — not what software produced them.
What Typically Triggers a Platform Switch
The most common reasons B2B companies switch sales tax platforms:
- Mergers or acquisitions result in different tax platforms being used within the organization
- The current platform has become too expensive
- Certificate management is missing or requires manual intervention
- Use tax accrual is not handled, leaving AP review to spreadsheets
- Audit documentation is not organized or retrievable by jurisdiction
- The platform was built for transaction volume and not B2B exemption complexity
- Implementation and support costs have grown beyond the value delivered
Each of these is a legitimate reason to switch. None of them make the migration simpler.
What You Need to Migrate Before You Go Live
-
1Historical transaction records
Every taxable and exempt sale for the full audit lookback period needs to be exportable, organized, and retrievable in the new system. This means transaction date, customer, jurisdiction, product, tax collected, and rate applied. If the old platform stores this data in a proprietary format, confirm with your new vendor how that data will be imported and in what format it will be searchable before you sign.
-
2Exemption certificates — active and expired
Certificates that are currently active need to migrate with their associated transaction records. Certificates that have already expired still need to migrate — you are legally required to retain them for the audit lookback period even though they are no longer valid for new transactions. This is where most migration plans have gaps. See the next section for why this requires specific planning.
-
3Filing history and jurisdiction registrations
Copies of filed returns, payment confirmations, and nexus registration documentation for every state where you have been active. Many platforms generate this documentation on demand within the system. Before migrating, export it. Assume that the old platform will not remain accessible after conversion.
-
4Calculation methodology documentation
Historical tax rates and taxability rules in effect at the time of each transaction. If rates or rules have changed since those transactions occurred, an auditor may ask you to justify past calculations under the rates that applied then — not the rates that apply now. AUTOSOLV retains this documentation automatically through batch processing. See the AUTOSOLV audit defense overview for how historical rate documentation is stored and retrieved.
ACTSOLV stores certificates, transaction records, and audit documentation independently of any billing or ERP platform — so compliance records survive platform changes without interruption.
Talk to an ACTSOLV ExpertThe Exemption Certificate Problem No One Warns You About
Certificates stored in your current platform do not automatically transfer in a format that is useful in a new system. They may export as image files, PDFs without metadata, or structured data that doesn't map to the new platform's schema.
When that happens, you have three problems at once: active certificates that need to be validated in the new system, expired certificates that need to be retained but can't be linked to their original transactions, and customers who may need to reissue certificates because the original records are no longer accessible.
Contacting customers to reissue certificates mid-migration is disruptive and sometimes unsuccessful. Customers who have changed their tax status, moved states, or are simply unresponsive may not provide replacement documentation. If an auditor then asks for certificates supporting exempt sales from three years ago, a gap in the record is treated as a taxable sale.
The ACTSOLV case study on missing exemption certificates shows the assessment exposure this gap creates. The scenario is almost identical to what platform migrations produce when certificate continuity isn't planned for.
The CertSOLV approach: CertSOLV manages certificate storage, validation, and renewal independently of any billing or ERP platform. Certificates are tied to transaction records and retained in a retrievable format regardless of what platform changes occur downstream. See the guide to handling expired and invalid exemption certificates for retention requirements in detail.
Questions to Ask Any Sales Tax Platform Before You Sign
Evaluate any new platform against these questions before committing to a migration. A vendor that cannot answer them clearly before the contract is signed will not answer them more clearly during a migration or an audit.
On historical data
- How does the platform export historical transaction data, and in what format?
- Can exemption certificates be imported with their associated transaction records — not just as standalone files?
- How are expired certificates retained and linked to original exempt transactions?
On use tax and AP processing
- What is the batch processing cycle for AP invoice review and use tax accrual?
- How is historical tax rate and taxability methodology documented and retrievable for audit?
On migration and exit
- What does the migration process involve, and who manages it?
- If we need to exit this platform in the future, how do we get our data out?
The answer that should give you pause: "Your historical data will be available in the system." Ask specifically: in what format, searchable by what fields, and exportable how? Vague answers about data availability before a contract is signed become unavailable answers after it is signed.
How ACTSOLV Is Built for the B2B Compliance Use Case
CertSOLV
Handles exemption certificate management independently of any single billing or ERP system. Stores certificates, tracks expiration, validates state-specific requirements, and retains historical records in a format that survives platform changes.
AUTOSOLV
Handles use tax accrual on vendor purchases through batch processing of AP data across all major platforms. Retains transaction records, rate documentation, and jurisdiction-level filing history for the full audit lookback period.
Neither product requires the kind of deep ERP integration that makes migrations complex. Batch processing means your existing AP and billing workflows feed the compliance layer without being rebuilt around it. See how ACTSOLV compares to other sales tax platforms on the compare sales tax software page.
Frequently Asked Questions: Switching Sales Tax Platforms
What happens to my historical records when I switch platforms?
That depends entirely on your migration plan. Records that are not exported, organized, and imported into the new system before go-live may be inaccessible once the old system is decommissioned. Before switching, export all historical transaction records, exemption certificates, filing history, and calculation methodology documentation. Confirm with your new vendor that the exported data can be imported and searched in the new system.
Do I need to keep expired exemption certificates after switching platforms?
Yes. Exemption certificates must be retained for the duration of your audit lookback period regardless of whether they are still valid. Most states have a three-to-four year lookback window. An expired certificate that was valid at the time of the transaction still supports the exempt treatment of that transaction in an audit — but only if it is retrievable and linked to the original sale.
Can an auditor look at transactions from before I switched platforms?
Yes. A state audit covers the full lookback period regardless of what system you were using during that time. The auditor does not care which platform generated your records. They care whether the records exist and whether they support the tax treatment applied to each transaction.
What is the biggest mistake companies make when switching sales tax platforms?
Treating the migration as a technology project rather than a compliance project. The technical go-live is the easy part. The hard part is ensuring historical records, certificate files, and filing documentation are complete, organized, and transferable before the old system goes dark. The second most common mistake is not accounting for exemption certificate continuity. See the 5 red flags in your exemption certificate process for the warning signs to check before and after a migration.
Switching Platforms? Start with a Compliance Review.
ACTSOLV can assess your current certificate and use tax records before you migrate — so you know exactly what needs to transfer and what the gaps are before go-live.
