From Mfg/Pro to QAD Enterprise Edition without losing data

The situation

A manufacturer had been running QAD Mfg/Pro for years. The system worked — that was the problem. It worked well enough that the upgrade to QAD Enterprise Edition kept sliding down the priority list, while the version fell further behind on vendor support, and the finance module gap between old and new grew wider. Meanwhile the accounting team compensated with side spreadsheets for everything the old version couldn’t do. Every year of waiting made the eventual move bigger.

The work

This engagement came out of the founder’s years in QAD’s own professional services group, where facilitating Mfg/Pro-to-Enterprise Edition upgrades was the day job. The pattern that works:

• Map the finance configuration first. Enterprise Edition’s financial architecture differs meaningfully from Mfg/Pro’s — chart of accounts, entities, and posting logic all need deliberate design decisions, not a lift-and-shift.
• Migrate data in rehearsals, not once. Trial migrations with reconciliation back to the old system — trial balances tie out, open items match, inventory values agree — before anyone commits to a cutover date.
• Rebuild reporting on purpose. Financial report models were designed in QAD’s finance report writer to match how management actually read results, instead of recreating every legacy report by reflex.
• Train before go-live, not after. Finance users worked through the new functionality — including capabilities Mfg/Pro never had — on their own data, before the switch.

How it played out

Because the data had been reconciled in rehearsal, go-live was an anticlimax — which is the goal. The measure of an ERP upgrade isn’t the go-live party; it’s whether the first month-end close on the new system runs without surprises, and whether the side spreadsheets start disappearing because the system now does that work.

What it means for a business like yours

If you’re a Colorado manufacturer sitting on an old ERP version — Mfg/Pro, an early SyteLine, or similar — the risk isn’t just missing features. It’s running your operation on software the vendor is winding down support for, with fewer people who know it each year. QAD’s own product documentation describes where the platform has gone; the upgrade path is well-trodden and typically runs a few months for a single-site business, not years.

Next step

Read about our [[ERP consulting]] — assessment of your current version and a realistic upgrade plan is where every one of these projects starts.