How to Switch Trade Compliance Software (Migration Playbook)
What changed: Rewritten for starting from spreadsheets or no ERP; record retention re-checked against 19 CFR 163.4 and 163.6; retired product claims removed.
To switch trade compliance software without losing records, send the non-renewal notice on time, export every classification record and its reasoning before the old contract ends, clean the product data, run old and new side by side on a sample, check migrated HTS codes and duty rates before go-live, and archive the old records for the full retention period. For a manager moving 8,000 SKUs off spreadsheets and an old GTM module with 120 days to renewal, records are the hard part: 19 CFR 163.4 keeps most of them in scope for five years from the date of entry.
In this post
- How do you switch trade compliance software without losing records?
- When is it time to move off spreadsheets or an old GTM module?
- Is 120 days enough to switch before the contract renews?
- What should you export before the old contract ends?
- How do you start when an entity has no ERP or the data is messy?
- Should you run the old and new systems side by side?
- How do you check migrated HTS codes and duty rates before go-live?
- How long must you keep the old system's records?
- What does switching cost?
- How does a switch to GingerOS run?
- Planning your switch
- References
I'm Chen Cui, co-founder of GingerControl. We build GingerOS, the AI trade compliance platform that runs on your process and the data you have, ERP or not, so a project can start exactly here: a spreadsheet, an old module and a renewal date. This post is about the switch itself. For choosing the new system, see our trade compliance software buyer's guide; for the questions to put to any vendor, the 20-point buyer's checklist.
How do you switch trade compliance software without losing records?
You switch without losing records by getting every record out of the old system, in a format you can open without it, before you stop paying for it. Everything else in a migration can be redone; a lost classification history cannot.
- NoticeRead the renewal clause and send notice first
- ExportCodes, reasons, history, certificates, logs
- CleanOne row per part and entity, every gap flagged
- Side by sideOld and new on a sample, differences decided
- CheckCodes and duty rates against recent entries
- ArchiveOld records kept for the retention period
With 120 days to renewal, here is a suggested schedule; the order matters more than the speed:
| When | Step | What goes wrong if you skip it |
|---|---|---|
| Week 1 | Read the renewal and notice clauses; send notice as the contract requires | The old contract renews for another term |
| Weeks 1 to 4 | Export every record and test that the files open | Access ends before you notice a missing field |
| Weeks 2 to 8 | Clean the product data; set up the new system | Old errors move into the new system with a new date on them |
| Weeks 6 to 14 | Run old and new side by side on a sample | A wrong rate goes out on a live entry |
| Before go-live | Check migrated codes and duty rates | A missing Chapter 99 line underpays duty on a filed entry |
| After go-live | Archive the old records | CBP asks for a record you can no longer open |
When is it time to move off spreadsheets or an old GTM module?
It is time when your files can no longer tell you why a code was chosen, or which parts a new rule hits. Spreadsheets hold codes well and reasons badly: the copy for one entity drifts from the copy for another, and nobody is told when a tariff change touches row 4,312.
Three signs come up again and again:
- The same part has two codes. Different entities or brokers classified it separately. We wrote up the fix in same product, different HS codes across entities.
- Every rule change is a manual search. Someone filters the sheet by heading after each notice and hopes the filter was right.
- Nobody can show the reasoning. When CBP sends a CF-28, the answer has to be rebuilt from email. See answering a CF-28 with your classification history.
An old GTM module fails differently: it often keeps the record but sits apart from the plants and suppliers where changes start. Legacy GTM sprawl and the data layer covers when to add a layer instead of replacing everything.
Is 120 days enough to switch before the contract renews?
Usually yes, if the notice goes out in the first week and the export starts in the first month. The switch itself is rarely the slow part; finding out in month three that a field never exported is.
Our own GingerOS projects have typically run 8 to 16 weeks from first call to go-live, and the first two of their five phases come before any contract [5]. That fits inside 120 days when the records leave the old system early and the cleanup starts at the same time. If the notice window has already passed, ask the old vendor in writing for a short extension or a shorter term, and keep exporting while you negotiate.
What should you export before the old contract ends?
Export everything that explains a past decision, not only the current code list. CBP asks about entries you already filed, so the record that matters is the one that shows what you knew on that date.
| Record | Why you need it | Check before access ends |
|---|---|---|
| Each part's HTS code, with the date it was set and who approved it | Shows the code in force on each entry | Dates and approvers came out, not just codes |
| The reason behind each code: rules, notes and rulings cited | Your reasonable-care record | Free-text notes and attachments came out too |
| Code history: old codes and when they changed | Explains entries filed under an earlier code | Changed rows keep both values |
| FTA and origin documents, supplier certificates | Support preference claims on past entries | Expiry dates survived the export |
| Rulings you hold | Bind the classification of specific goods | Ruling numbers link to the parts |
| User and approval logs | Show who decided what, and when | Timestamps kept their time zone |
Ask the vendor for the export format in writing, and open each file without their software before you send the final notice. Your filed entries also live in CBP's ACE, and the ES-003 report lets you pull them line by line to compare with what the old system says.
How do you start when an entity has no ERP or the data is messy?
You start from whatever the entity has: spreadsheets, emails, PDFs and supplier files are enough to begin. A new system does not need an ERP underneath it, and messy data is a cleanup task, not a reason to wait.
In a GingerOS project, an entity without an ERP gets a data storage environment and a data flow designed for its team. Messy data is cleaned and organized first, then we build the AI system on it [5]. GingerOS reads emails, PDFs, Excel files and images; it does not read video [6].
The cleanup itself is plain work:
- One row per part and entity, with duplicate part numbers merged.
- Every code without a recorded reason flagged, not deleted.
- Missing facts listed (material, function, how the part is used), because those decide the code. After go-live, GingerOS asks for a missing fact before it suggests an HTS code.
If the entity came with an acquisition, check its past entries separately; our M&A trade compliance due diligence guide explains why. For the supplier side of messy data, see why supplier data quality decides classification accuracy.
Should you run the old and new systems side by side?
Yes, on a sample, until every difference has a decision. Pick the parts you ship most and pay the most duty on, run both, and file from the old process until the new one agrees or a person has decided which is right and why.
Two rules keep the side-by-side run honest:
- A difference is a question, not an error report. Sometimes the new system is right and the old code was wrong for years. That is worth knowing, and worth a careful look at past entries with your broker.
- Do not migrate everything at once. Move in batches, by entity or product family, and sign off each batch. Inactive parts can wait or go straight to the archive.
If a wrong rate does go out during the switch, your broker can correct an unliquidated entry with a post summary correction, filed within 300 days of the date of entry and at least 15 days before the scheduled liquidation date, whichever comes first, while CBP is not reviewing the entry [7]. Once that window closes, the routes are a protest after liquidation or a prior disclosure.
How do you check migrated HTS codes and duty rates before go-live?
Compare code by code, then recompute duty for a sample of recent entries and set it against what was filed. A migrated code list can look right and still carry an old rate table.
Check every U.S. layer for each entry date, not just the base rate:
- The base MFN rate, each Section 232 and Section 301 line, other Chapter 99 lines, MPF and HMF.
- The forced-labor Section 301 on goods entered from July 24, 2026: 10% or 12.5% depending on the country (net of the MFN rate for some, such as the EU and Japan), with exemptions for some Section 232 articles and USMCA goods [4].
- Section 122, only for entries from February 24 to July 23, 2026 [3]. A rate table that still adds it after that date is a red flag; see Section 122 explained.
For a Japanese sourcing option, U.S. import tariffs and customs costs for Japan separates agreement treatment from customs fees and product-specific surcharges.
For spot checks of one code at a time, the GingerLite Tariff Calculator shows each layer on its own line for the entry date you enter. For a structured review of the whole list, how to audit your existing HTS codes walks through it.
How long must you keep the old system's records?
Five years from the date of entry for most records, under 19 CFR 163.4(a). Drawback records stay until the third anniversary of the claim's payment, and packing lists have a shorter period of their own [1].
When CBP demands entry records, they are due within 30 calendar days of receiving the demand, or sooner where admissibility or release depends on them. Failing to produce a record on CBP's list of entry records can cost, for each release of merchandise, up to $10,000 or 40% of the merchandise's appraised value when negligent, and up to $100,000 or 75% when willful, whichever is less [2]. A system switch changes none of this. Archive the old records where you can open them without the old vendor, and write down where they are. The full rules are in our 19 CFR 163 recordkeeping guide.
What does switching cost?
Switching costs the overlap of two contracts during the side-by-side run, your team's time for the export and checks, the data cleanup, and the new system. The cleanup is the line most often missing from a quote, so ask every vendor whether it is included and how a messy entity is priced.
GingerControl quotes GingerOS per project, after the Prototype Week, so the cleanup and the data flow for an entity with no ERP are in the quote before you sign. How each vendor type charges is compared in trade compliance software pricing models, and the payback math in the trade compliance software ROI calculator.
How does a switch to GingerOS run?
A switch to GingerOS starts with Prototype Week: one call about your process, a clickable prototype of your own flow in three days, a requirements meeting the same week, and a quote after. It needs no system access and no production data.
From there:
- Connections are set up per client: read-only, staged, no master data migration. GingerOS becomes the system of record for classification decisions, and ERP fields become downstream caches. Your IT team can see how on the IT page.
- Approved results go back to your ERP with an audit trail, and every SKU a rule, part or supplier change touches is rechecked.
- Classification asks for missing product facts before it suggests a code, and records the reasoning for your approval. Our classifications are for general reference, educational, and planning purposes; before a code goes on an entry, your licensed customs broker reviews it.
Planning your switch
Start with two dates: the contract's notice deadline and the day your export must be complete. If you want to see first where your entities, brokers and records disagree, the compliance audit is a 30-minute review that shows what to fix first. When you are ready to see your own flow, book the Prototype Week.
References
- Legal Information Institute, Cornell Law School, 19 CFR 163.4, Record retention period
Data cited: Records kept 5 years from the date of entry or of the activity; drawback records until the third anniversary of the date of payment of the claim; packing lists 60 calendar days from the end of the release or conditional release period
Source: 19 CFR 163.4
Published: read October 11, 2026 - Legal Information Institute, Cornell Law School, 19 CFR 163.6, Production and examination of entry and other records
Data cited: Entry records produced within 30 calendar days of receipt of the demand, or a shorter period for admissibility or release; failure to produce an (a)(1)(A) list record, for each release of merchandise: up to $100,000 or 75% of appraised value (willful), up to $10,000 or 40% (negligent), whichever is less
Source: 19 CFR 163.6
Published: read October 11, 2026 - Federal Register, Proclamation 11012, Imposing a Temporary Import Surcharge To Address Fundamental International Payments Problems (Section 122)
Data cited: 10% surcharge on goods entered from February 24, 2026 through 12:01 a.m. eastern daylight time on July 24, 2026
Source: Proclamation 11012
Published: February 25, 2026 - Federal Register, Office of the U.S. Trade Representative, Notice of Actions in Section 301 Investigations of Acts, Policies, and Practices of Various Economies (forced labor), 91 FR 47318
Data cited: Additional duties of 10% or 12.5% depending on the economy (for the EU and Taiwan, set so MFN plus Section 301 equals 10%; for Japan, Korea and Switzerland, 12.5%), on goods entered from July 24, 2026; exemptions include listed Section 232 articles and USMCA goods of Canada and Mexico entered free of duty
Source: 91 FR 47318
Published: July 28, 2026 - GingerControl, Business engagement: Trade Compliance Software Implementation, Phase by Phase
Data cited: Prototype Week (one call, a clickable prototype in three days, a requirements meeting the same week, a quote after); custom builds typically 8 to 16 weeks end to end; without an ERP, data storage set up and a data flow designed for the team; messy data cleaned and organized before the AI system is built
Source: GingerControl engagement page
Published: read October 11, 2026 - GingerControl, FAQ
Data cited: GingerOS reads anything in text or image form (emails, PDFs, Excel files, scanned documents and photos); video is not supported
Source: GingerControl FAQ
Published: read October 11, 2026 - U.S. Customs and Border Protection, Post Summary Corrections
Data cited: A post summary correction can be filed within 300 days from the date of entry and up to 15 days before the scheduled liquidation date, whichever is earlier; the entry summary must be accepted, paid, in CBP control, not under CBP review and not liquidated
Source: CBP, Post Summary Corrections
Published: last modified August 6, 2026; read October 11, 2026
Questions people ask
We still run trade compliance in Excel. When is the right time to move to software?
Move when the spreadsheet can no longer tell you why a code was chosen or which parts a new rule hits. For a team with 8,000 SKUs across several entities, that point usually arrives when the same part carries different codes in two files, or a tariff change means checking every row by hand. Software that keeps the reason with each code and rechecks the affected parts is the fix; a bigger spreadsheet is not.
Our GTM contract renews in 120 days. Is that enough time to switch?
Usually, if you send the non-renewal notice first and start the export in the first month. Read the notice clause on day one, because missing it can renew the contract for another term. GingerControl's GingerOS projects have typically run 8 to 16 weeks from first call to go-live, so 120 days fits when the records are out of the old system early and the data cleanup starts at the same time.
We missed the non-renewal notice date. What can we do?
Ask the vendor in writing for a short extension or a shorter renewal term while you finish the switch, and keep using the time to export and clean your records. Whatever the contract says, the records stay your responsibility: CBP can ask for most of them for five years from the date of entry, so plan the archive before the old access ends.
Our acquired entity has no ERP and keeps import records in email and Excel. Can it move onto a trade compliance system?
Yes. A system does not need an ERP to start. With GingerControl's GingerOS, an entity without an ERP gets a data storage environment and a data flow designed for its team, and GingerOS reads its emails, PDFs, Excel files and images (not video). The acquired entity's past entries still need a check of their own, because its codes may not match the rest of the group.
Our product data is messy. Can we still start?
Yes. Clean and organize the data first, then build on it: one row per part and entity, duplicates merged, and every code without a reason flagged. In a GingerOS project, GingerControl cleans and organizes the data before building the AI system, and after go-live GingerOS asks for any missing product fact, such as a material or a function, before it suggests an HTS code.
Can we keep using the old system or the spreadsheets during the migration?
Yes, and you should for a while. Run the old and new side by side on a sample of parts, weighted to the ones you ship most and pay the most duty on, and file from the old process until every difference has a decision and a reason on record. Turn the old system off only after the archive is complete.
Do we have to migrate every SKU at once?
No. Move in batches, by entity or product family, and sign off each batch before the next. For 8,000 SKUs, start with the parts on recent entries, because those are the codes CBP is most likely to ask about, and leave inactive parts for later or for the archive.
How long do we have to keep classification records after we switch systems?
Five years from the date of entry for most records, under 19 CFR 163.4; drawback records until the third anniversary of the claim's payment. On a CBP demand, entry records are due within 30 calendar days under 19 CFR 163.6. Switching systems does not change either rule, so export the old records in a format you can open without the old vendor.
How much does it cost to switch trade compliance software?
The real costs are the overlap of two contracts during the side-by-side run, your team's time for the export and the checks, the data cleanup, and the new system itself. Ask each vendor what its price includes for cleanup and the export from your old system. GingerControl quotes GingerOS per project, after the Prototype Week, so the cleanup a messy entity needs is priced before you sign.
Shortlisting AI for trade compliance?
Hand this to GingerOS.
Pick a 30-minute slot on the next page with Chen Cui, our CEO. Bring one notice or one SKU list (an ERP export, a spreadsheet or an email will do) and see what GingerOS does with it.
Reviewed by Michael Weick, LCB / CCS




