tradephlo.com

What does switching customs declaration software actually involve, and how do you avoid missing a filing deadline?

The real cost of switching customs declaration software is rarely the software. It is the handful of days around cutover when both systems are technically live and nobody is quite sure which one a given filing should go through. Here is what actually has to happen to move UK CDS and NCTS filing from one system to another without a gap.

What does switching customs declaration software actually involve, and how do you avoid missing a filing deadline?

By Saurabh Goyal, Founder & CEO of Phlo Systems. Published 20 November 2026.

Most UK importers, exporters, brokers and forwarders who are unhappy with their current customs declaration software stay with it anyway, for one reason: the switch itself looks riskier than the problem they already have. That fear is reasonable, because a badly run cutover can genuinely cause a missed filing. It is also, in most cases, avoidable, because the actual steps a switch requires are well understood and do not need to happen all at once.

The 30-second answer:

  • A customs declaration software switch is not a single event. It is a short list of discrete steps, most of which can happen before you file a single real declaration on the new system.
  • The two things that actually cause a missed filing during a switch are running both systems live for the same declaration type at the same time with no clear rule for which one is authoritative, and migrating historical data before the live filing path is proven.
  • HMRC does not require you to re-register for CDS or re-apply for EORI to change software provider; your approvals and authorisations sit with HMRC and your EORI, not with your current vendor.
  • A clean switch separates "prove the new system files correctly" from "stop using the old system," and does not do both on the same day.

What actually has to happen

A switch breaks down into a small number of steps, in a specific order, and the order matters more than the speed:

  1. Confirm your HMRC approvals travel with you. Your CDS access, EORI number, and any authorisations (simplified procedures, deferment accounts, special procedures) belong to your business, registered against HMRC and your EORI, not to your current software provider. Moving provider does not require re-registering for CDS or re-applying for an EORI. What does need setting up is the new provider's own connection to CDS on your behalf, and, if you use one, your duty deferment account linked correctly in the new system.
  2. Run a parallel test period before any live filing moves. The new system should file test declarations, or real declarations for a small, low-risk subset of your volume, while the old system continues to carry everything else. This is where you find out whether commodity codes, procedure codes, and party details are mapped correctly, before it matters.
  3. Pick a single cutover point per declaration type, not a gradual blend. The failure mode that actually causes missed filings is not switching too fast, it is leaving both systems technically able to file the same declaration type at the same time with nobody owning the decision of which one is authoritative on a given day. Decide, in writing, that import declarations move on a specific date and export or transit move on a specific (possibly different) date, and stop filing that type on the old system from that date, not gradually.
  4. Migrate historical records after the live path is proven, not before. You need access to past declarations for audits and post-clearance queries, but there is no requirement to have historical data loaded into the new system before you can file new declarations in it. Treat historical migration as a separate, lower-pressure project that happens once the live filing path has been running cleanly.
  5. Keep the old system accessible, not necessarily active, for a defined retention period. You will likely need to refer back to declarations filed on the old system for HMRC retention requirements. Confirm how long your old provider will give you read access after you stop filing with them, in writing, before you give notice.

Why most of the fear is about step 3, not steps 1 or 4

The two steps that sound hardest, HMRC re-approval and historical data, are usually the least risky in practice, because neither one is time-pressured: your approvals do not need re-doing, and historical data does not need to move before you can file. The step that actually causes problems is the live cutover itself, specifically the period where it is unclear which system is the filing system of record for a given declaration type. That is a process and communication problem inside your own team (and your broker's, if one files on your behalf), not a technical one, and it is the one worth the most planning attention.

Who should plan a switch, and who should not rush one

A switch is worth planning carefully if your current software cannot do something you actually need (a new country, a procedure type, NCTS transit, visibility into what a broker is filing on your behalf), or if the commercial terms no longer make sense for your volume. It is not worth rushing into mid-way through a busy filing period, or without a parallel test period, regardless of how attractive a new provider's terms are. The steps above do not change based on urgency; what changes is how much runway you give yourself to do them in order.

Frequently Asked Questions

Do I need to re-register for CDS or get a new EORI to switch customs software provider?

No. Your CDS access and EORI number are registered against your business with HMRC, not with your software provider. Switching provider means connecting the new provider to your existing CDS access and authorisations, not re-applying for them.

What is the single biggest cause of a missed filing during a software switch?

Running both the old and new systems as technically able to file the same declaration type on the same day, with no clear rule for which one is authoritative. The fix is a defined cutover date per declaration type, decided and communicated in writing, not a gradual blend.

Do I need my historical declarations migrated into the new system before I can start filing with it?

No. You can begin filing new declarations on the new system once it is proven to file correctly, and treat historical data migration as a separate project. What you do need is continued access to the old system, or an export of your records, for as long as HMRC's retention requirements apply.

How long should a parallel test period run before a full cutover?

Long enough to see your actual range of declaration types and edge cases go through the new system correctly, not a fixed number of days. A business with a narrow, repetitive declaration profile may be confident after a small sample; one with varied procedure types, origins, or special procedures should test each variation at least once before treating the new system as proven.

How Phlo Systems helps

tradePhlo Declarations is built to be switched to without a gap: your CDS filing connects to your existing HMRC approvals directly, a parallel test period runs alongside your current provider before any live filing moves, and historical records migrate on their own timeline once the live path is proven. See tradePhlo Declarations.


Related reading:

Saurabh Goyal is the Founder & CEO of Phlo Systems. He spent 12 years building CTRM and ERP systems for global commodity trading houses before founding Phlo in 2016.

Want to learn more about Phlo Systems?

See how our platform digitises international trade for commodity traders, importers, and exporters.

Get Started