Teams stay on sales tax software they have outgrown because they fear the migration. A botched switch loses exemption certificates and misfiles returns, and a missed filing during cutover creates real sales tax penalty exposure. This checklist walks the full transition, from vendor evaluation to post-migration reconciliation, with zero downtime.
The core answer sits here. Evaluate, prepare, migrate, run both systems in parallel, validate, then cut over at a filing period boundary. Here is the sequence at a glance.
| Phase | Action | Timing |
|---|---|---|
| Evaluate | Audit gaps, score vendors against a requirements matrix | Weeks 1-2 |
| Prepare | Assign one owner, secure buy-in, write the migration plan | Weeks 2-3 |
| Migrate | Export and archive five data categories, build the tax code crosswalk | Weeks 3-4 |
| Parallel run | Shadow-calculate on the new system while the old one files | One full filing period |
| Validate | Reconcile calculations and first filings against the old system | Go-live week |
| Go-live | Cut over at a filing period boundary, monitor first filings | Period boundary |
Why Do Businesses Switch Sales Tax Software?
Businesses switch because of rising costs, opaque pricing, weak support, missing nexus alerts, and clunky enterprise resource planning (ERP) integrations. The usual trigger is expansion into new states, which made economic nexus tracking mandatory in practice after the Supreme Court decided South Dakota v. Wayfair, Inc. on June 21, 2018.
The Wayfair decision, a 5-4 ruling, overruled the physical-presence rule as “unsound and incorrect,” which is why multi-state nexus tracking is now a core software feature. The United States has no federal sales tax. Forty-five states plus the District of Columbia levy one, and 37 also allow local rates (U.S. Government Accountability Office), producing 10,000 to 12,000 taxing jurisdictions nationwide (U.S. Government Accountability Office). Rates run from New Jersey’s single 6.625% statewide rate (New Jersey Division of Taxation) to a Texas maximum combined rate of 8.25% (Texas Comptroller).
Avalara is the dominant incumbent most searchers evaluate alternatives to. Its real strengths are broad jurisdiction coverage and a large integration ecosystem. Teams still leave when pricing scales with transaction volume or when a legacy integration cannot model their data. State rules also move, which forces mapping updates.
| Rule | Detail | Source |
|---|---|---|
| South Dakota v. Wayfair | Decided June 21, 2018, 5-4; overruled the physical-presence rule | U.S. Supreme Court |
| South Dakota threshold | $100,000 gross sales; 200-transaction test removed effective July 1, 2023 | South Dakota DOR |
| California threshold | $500,000 in sales, no transaction count, effective April 1, 2019 (AB 147) | California CDTFA |
| Texas threshold | $500,000 in total Texas revenue over the preceding 12 months | Texas Comptroller |
The DOR (Department of Revenue) in each state sets and updates these numbers. The foundations of US sales tax compliance explain why getting the migration right protects you against back-tax liability.
How Do You Prepare for a Sales Tax Software Transition?
Audit your current gaps, define requirements, assign one internal owner, secure leadership buy-in, and write the data migration plan before signing anything. Preparation is what turns a risky cutover into a managed project. Five short steps get you ready to evaluate vendors and move data without disrupting billing.
- Audit current workflows to document manual tasks, error rates, and missing features.
- Define requirements so success is measurable, such as faster filings and real-time calculation.
- Assign one owner in finance or operations to coordinate demos, migration, and communication.
- Secure leadership buy-in with a cost-benefit case covering time saved and audit defense.
- Write the data migration plan mapping every field before you sign a contract.
What Should You Look For When Choosing New Tax Software?
Score vendors against a fixed requirements matrix of functional capabilities, not against demos. A demo shows the happy path. A matrix forces you to verify the capabilities that break during real filings. Test each requirement in a sandbox trial before you commit. If you are unsure switching software alone solves the problem, weigh it against sales tax compliance outsourcing.
| Requirement | What to verify | Why it matters |
|---|---|---|
| Multi-state nexus tracking | Economic nexus alerts fire at each state threshold | Missed thresholds create back-tax liability |
| Real-time calculation | Accurate rates for SaaS and digital goods by jurisdiction | Wrong taxability under- or over-collects |
| API and ERP integration depth | Native connectors sync customers, exemptions, transactions | Manual exports break at volume |
| Automated return preparation | One-click e-filing with per-return status tracking | Removes the manual step where deadlines slip |
| Built-in filing calendar | Due-date reminders and status per jurisdiction | Prevents missed filings |
| Audit trail | Every rate change and calculation is logged | Defensible records during an audit |
| Exemption certificate management | Metadata for expiration, jurisdiction, and type | A lost certificate makes the seller liable |
| Transparent pricing | A published, predictable model | Volume-based pricing spikes as you grow |
| Support responsiveness | A named escalation path during filing deadlines | Help arrives when a filing is due |
API stands for application programming interface, the connection that syncs data between systems automatically.
What Is the Step-by-Step Checklist for Switching Sales Tax Software?
Follow ten steps, from auditing the current provider to monitored go-live, sequenced around a filing period boundary. Each step produces an output or a rollback trigger, so you always know whether to proceed or hold. The deep-dive sections below expand data migration, tax code mapping, the parallel run, and validation.
| Step | Action | Output / rollback trigger |
|---|---|---|
| 1 | Audit the current provider’s gaps | Documented requirements list |
| 2 | Score vendors against the requirements matrix | Selected vendor |
| 3 | Secure buy-in and assign one owner | Signed migration plan |
| 4 | Export and archive five data categories | Secure archive; abort if export is incomplete |
| 5 | Build the product tax code crosswalk | Validated code map; abort if rates diverge |
| 6 | Configure and sandbox test the new system | Passing test matrix |
| 7 | Run both systems in parallel for one filing period | Clean reconciliation; hold cutover on variance |
| 8 | Validate calculations against historical results | Variance within the set threshold |
| 9 | Cut over at a filing period boundary | Old system kept read-only |
| 10 | Monitor first live filings and reconcile | Reconciled first return |
How Do You Migrate Sales Tax Data Between Providers?
Export and archive five data categories before touching the new system. Most states can audit three to four years back, and lost records become your liability. Export historical transactions, exemption certificates, nexus registrations, filing history, and product tax code assignments, then store a secure archive for rollback and audit defense.
| Data category | What must transfer intact | Risk if lost |
|---|---|---|
| Historical transactions and calculations | Every line, rate, and jurisdiction | No audit defense |
| Exemption certificates plus metadata | Expiration, jurisdictions, certificate type | Seller becomes liable for uncollected tax |
| Nexus registrations | Registration numbers, filing frequencies, portal credentials | Returns file to the wrong account |
| Filing and remittance history | Prior returns and payments | Cannot reconcile at go-live |
| Product tax code assignments | Per-SKU taxability mapping | Silent recalculation errors |
Exemption certificates are the highest-risk category. A lost or unlinked certificate makes the seller liable for uncollected tax during an audit. The retention window is set by each state’s statute of limitations.
| State | Audit lookback | Source |
|---|---|---|
| California | 3 years; 8 years if no return filed | California CDTFA, Rev. & Tax. Code §6487 |
| Texas | 4 years from the due date | Texas Comptroller audit manual, Tax Code §111.201 |
| Washington | 4 years from close of the tax year | Washington RCW 82.32.050 |
| New York | 3 years; unlimited for non-filers or fraud | New York Tax Law §1147 |
| Florida | 3 years; unlimited for non-filing or fraud | Florida Statutes §95.091 |
How Do You Preserve Product Tax Code Mappings?
Vendor tax code taxonomies are proprietary and never map one-to-one, so build a crosswalk per stock keeping unit (SKU) or product line and validate every mapped code against known-correct historical calculations. This is where recalculation errors originate, because a wrong mapping silently changes taxability by jurisdiction. Validate, do not assume equivalence.
Avalara uses proprietary codes such as SW054000 for SaaS and software. The new vendor’s taxonomy differs. Run the same transaction through both systems and compare the calculated rate before you trust a mapped code. Clean the catalog first by deduping customers, fixing invalid addresses that route to the wrong jurisdiction, and archiving obsolete SKUs.
How Do You Migrate From Avalara Without Downtime?
Export transaction history, exemption certificates from CertCapture, and registration details before the contract lapses, keep read access through one overlap period, and cut over at a filing period boundary. Use the contract renewal date as your planning anchor, and start data export well before it, so nothing is stranded when access ends.
Avalara’s coverage and integration ecosystem are genuine strengths, so plan the offboarding as carefully as the onboarding. Pull certificate metadata, product tax code assignments, and state registration numbers using Avalara’s own export tools. Keep the old account read-only for the length of the audit statute so historical records stay reachable.
Should You Run Parallel Sales Tax Systems During Migration?
Yes. Run both systems for one full filing period. The old system files while the new one shadow-calculates, and discrepancies surface before they reach a return. Any delta in calculated tax points to a mapping or configuration error you fix before cutover. Parallel running is what makes the migration zero-downtime, because no period goes uncovered.
How do you sandbox test your sales tax configuration?
Configure taxability rules, nexus settings, and integration endpoints in staging, then replay real historical transactions and compare outputs to the old system. Cover multiple states, taxable and exempt scenarios, and every billing model you use: one-time, recurring, and usage-based. Watch for rounding differences, destination-versus-origin sourcing, and taxability differences on digital products.
How Do You Validate Tax Calculations After Switching?
Reconcile a statistically meaningful sample of new-system calculations against old-system results line by line, set an acceptable variance threshold, and investigate every exception before the first live filing. The numbers should match within tolerance. Any variance signals a tax code mapping error, an address-sourcing difference, or a rounding issue that must be resolved first.
How do you reconcile sales tax filings after migration?
Compare the first cycle of new-system returns against prior-period filings and remittance records per jurisdiction, confirm filing frequency assignments match state registrations, and verify the compliance calendar rebuilt correctly. Reconcile collected tax from billing against tax reported in the new system, and resolve every gap before you remit.
How Do You Train Your Team and Notify Stakeholders Before Go-Live?
Document new workflows in updated standard operating procedures (SOPs), train your finance, sales, and operations teams hands-on, and notify external partners before go-live. Tell your certified public accountants (CPAs), bookkeepers, and payment processors about the change, and update service agreements and integration credentials. Clear training and communication prevent adoption stalls and surprise breakages when filings start flowing through the new platform.
Your SOPs should cover how to add new nexus states or products, how to generate and review returns, and how to handle exemptions and audits. On the communication side, update vendor contacts and any electronic data interchange (EDI) or API credentials so nothing breaks when the new platform goes live.
What Are the Real Costs of Switching Sales Tax Software?
Budget for three cost buckets: implementation and internal hours, one overlap period of double subscription during the parallel run, and remediation of any mapping errors found in testing. Frame the decision as total cost of ownership across fees, advisor time, and risk exposure. This is why transparent, published pricing is an evaluation criterion, not a nice-to-have. Volume-based models spike as you grow, so ask each vendor to model your cost at higher transaction counts.
How Does the Checklist Change for Ecommerce, SaaS, and Multi-Entity Companies?
The core checklist holds, but the highest-risk data category differs by business model. Ecommerce sellers worry about channels and physical nexus, SaaS companies worry about inconsistent taxability, and multi-entity groups worry about per-entity separation. Adjust the verification steps accordingly.
What should ecommerce businesses check before switching?
Marketplace facilitator laws shift collection to marketplaces like Amazon and Etsy in most states, so verify the new system distinguishes marketplace from direct-channel transactions. California, for example, required marketplace facilitators to collect starting October 1, 2019 (California CDTFA). Confirm the system handles physical nexus from Fulfillment by Amazon (FBA) inventory, and review the best sales tax software for ecommerce.
What should B2B SaaS companies check before switching?
SaaS (Software-as-a-Service) taxability is inconsistent, and roughly 20 or more states tax it, so verify your SaaS-specific tax codes map correctly. Some states tax SaaS and others do not, which makes a wrong code map costly.
| State | Taxes SaaS? | Source |
|---|---|---|
| New York | Yes | New York Dept. of Taxation and Finance |
| Texas | Yes, as data processing | Texas Comptroller |
| Pennsylvania | Yes | Pennsylvania Dept. of Revenue |
| Washington | Yes | Washington Dept. of Revenue |
| California | No | California CDTFA |
| Florida | No | Florida Dept. of Revenue |
What should multi-entity companies check before switching?
Per-entity registrations, filing calendars, and consolidated reporting must migrate per entity, never merged. Each legal entity carries its own nexus footprint and filings. Confirm the platform separates entities while still rolling up consolidated reports, and see sales tax compliance for multi-state businesses for the multi-jurisdiction detail.
What Common Pitfalls Should You Avoid When Switching Tax Software?
Six failure modes cause most botched switches. Build a checkpoint against each into your plan.
- Losing exemption data, which exposes you to audit liability on exempt sales.
- Misreporting from skipping the parallel run, which hides discrepancies until a return is wrong.
- Underestimating timelines, which forces a rushed, error-prone rollout.
- Leaving integrations untested, which breaks real-time calculation at go-live.
- Skipping change management, which stalls adoption without a dedicated owner.
- Cutting over mid-period, which risks a missed deadline without a fallback plan.
How Commenda Makes Switching Sales Tax Software Seamless
Commenda’s global indirect tax software gives you a guided onboarding that migrates past filings, nexus registrations, and exemption certificates, plus multi-state nexus tracking with economic nexus alerts so no threshold slips past you. It maps each product’s tax code once, then applies correct rates across US jurisdictions and internationally, with ongoing content updates.
Commenda supports 100+ ERP, API, and custom integrations, including NetSuite, Shopify, BigCommerce, and Amazon, so ecommerce and SaaS teams migrate without re-architecting their data model. Use the US nexus exposure guide as your canonical threshold resource, and the sales tax calculator for quick rate lookups.
Book a demo to get a free migration assessment and nexus exposure review before you switch.
