How Ezurio Preserved AP Continuity Migrating QAD to NetSuite

ERP migrations are not rare. On average, a company changes its ERP platform every five to ten years, and each change puts the finance team’s daily work at risk.

For Ezurio, the move from QAD to NetSuite raised an immediate question for accounts payable: how do you modernize the core system without losing years of invoice history or forcing the AP team to relearn its job? DocLib had been the single, consolidated way AP ran across Ezurio’s global footprint since 2016, so keeping that continuity mattered as much as the migration itself.

“When we transitioned from QAD to NetSuite, DocLib supported the entire process while preserving our invoice history.” -VP of IT, Ezurio

The challenge: a modern ERP without losing history or process

Ezurio was running a very old, on-premise version of QAD, first implemented in 2008. Business constraints, license constraints, and risk management concerns all pointed toward a more modern platform. NetSuite fit Ezurio’s distribution model and checked the boxes on ease of use, ease of implementation, and cost.

The complication sat in accounts payable. NetSuite’s native AP automation did not support Ezurio’s global footprint, specifically its multi-country, multi-currency, and multi-subsidiary operations.

There was also history to protect. In DocLib, invoices are stored as PDF documents with fully searchable metadata for historical reporting and audit, and the team did not want to lose any of that in the move. The two systems are also built differently. QAD’s concepts of receivers and vouchers do not translate cleanly to how NetSuite uses item receipts, vendor bills, and purchase orders, so workflows would not simply carry across on their own.

The impact was clear:

• A very old, on-premise QAD version, first implemented in 2008, with license and risk constraints
• Native NetSuite AP automation that did not support multi-country, multi-currency, or multi-subsidiary operations
• Years of searchable invoice history and audit metadata at risk in the migration
• QAD concepts that did not map cleanly onto NetSuite’s data model
• A global AP team that could not absorb a disruptive relearning of its process

The goal

Ezurio set out to modernize without giving up what already worked. The VP of IT, David England, wanted a platform someone else hosts, manages, and upgrades on a regular cadence, with governance around what can and cannot be customized, because the prior on-premise QAD version had been customized all the way down to the source code. The team’s objectives included:

• Move to a modern, vendor-hosted ERP that Oracle and NetSuite manage and upgrade on a regular cadence
• Rely on configuration and standard patterns like workflows and scripts, not deep source-level customization
• Keep the AP process and end-user experience consistent to reduce change on the AP team
• Preserve all historical invoice data and searchable metadata for reporting and audit
• Maintain one consolidated AP process across every country, currency, and subsidiary
• Avoid an approach that would block future growth, whether through new products or acquisitions

The results

• A NetSuite-native DocLib integration built around item receipts, vendor bills, and purchase orders
• Real-time access to invoice workflows and documents directly from vendor bills in NetSuite, without searching across systems
• An end-user experience that stayed very similar, so the AP team faced minimal retraining
• Years of invoice history and searchable metadata preserved and available for reporting and audit
• One consolidated AP process maintained across the multi-country, multi-currency, multi-subsidiary footprint

The impact

The migration moved Ezurio to a modern platform without disrupting accounts payable. History stayed intact and searchable, the AP team kept a familiar process, and the global AP function kept running as one operation while the business moved onto a platform built for a regular upgrade cadence and future growth.

Because DocLib already fit a global, multi-entity footprint, Ezurio avoided a common trap: choosing native tooling that works for a smaller footprint today, then being forced onto a partner later when a new currency, subsidiary, or acquisition arrives. David’s advice for teams planning an ERP change is to think carefully about everything you want the change to accomplish and about your growth strategy over the next several years, to choose a platform that supports where the business is going rather than only where it is today, and to understand the AP process in the new ERP early so you can avoid rework later in the project.

Watch the full interview here of the VP of IT at Ezurio, David England.

Curious to see what the ROI on AP Automation would look like for your team? Find out here.