
How to migrate from QAD to Sage X3
To migrate a client from QAD to Sage X3 with superglue's AI agent, connect the client's QAD database, and give superglue access to the client's Sage X3 account. superglue assesses the data in minutes, plans every phase, recommends an answer to each decision, and runs trial loads that reconcile to the cent before cutover. You review, decide and sign off with the client.
This guide covers QAD on premise: Enterprise Edition, Standard Edition and older MFG/PRO releases, and QAD Adaptive ERP where the client runs it on its own servers. QAD renamed QAD Enterprise Applications to QAD Adaptive ERP in 2019.
What are the steps to migrate from QAD to Sage X3?
Migrating from QAD to Sage X3 takes six steps: connect both systems, assess the data, plan every phase, decide the mapping, run trial loads and cut over. Each load repeats exactly what you tested, and every write waits for your approval.
- 01
Connect QAD and Sage X3
Connect the QAD database on Progress OpenEdge read-only through the OpenEdge ODBC driver on a Windows machine in the client's network. superglue writes nothing, and the client keeps working in QAD until cutover. The client then gives superglue access to Sage X3.
- 02
Assess the QAD data
In minutes, superglue counts every record, finds the open items and lists the data issues with examples. You know the size of the migration before you quote it.
- 03
Plan every phase
superglue drafts the plan from discovery to cutover, with tasks, owners and the QAD specifics already in it.
- 04
Decide the mapping
superglue brings each decision below with a recommendation from the client's own data. You confirm or change each answer, and the client signs the mapping.
- 05
Run the trial loads
superglue loads a Sage X3 test folder and compares it with QAD: the trial balance per period, the open receivables and payables per customer and vendor, the uncleared bank items, and the inventory value. superglue explains every difference, and you repeat the trial load until a full run reconciles with no new differences. The last run is a timed rehearsal of the cutover.
- 06
Cut over
At cutover, the client stops entry in QAD, and superglue loads the open items with the same steps as the trial loads. After the client closes the last period in QAD, superglue loads the final balances, and you sign the reconciliation with the client.
How do you get the data out of QAD?
- The superglue gateway runs on a Windows machine with the OpenEdge ODBC driver installed, and reads with a SQL user that can only read.
- QAD fields often hold values longer than the width the database reports over SQL, and those reads fail. Ask the client's database administrator to run the DBTool SQL width scan and fix before the first extract.
- Ask which domains and entities are in scope, because one QAD database can hold several companies.
- The client keeps working in QAD until cutover.
The client installs the superglue gateway once: Connecting to on-prem systems
What needs to be configured in Sage X3?
The client adds a Sage X3 user for superglue and names the folder superglue loads into. superglue configures Sage X3 and loads the data through that access, in a Sage X3 test folder first, in this order:
- 01
The charts of accounts and the analytical dimension types.
- 02
The ledgers and the account core model.
- 03
Companies and sites, with the legislation and the currencies of each company.
- 04
The fiscal years and periods of each company, and the dimension values.
- 05
Accounting codes, payment terms and tax codes.
- 06
Customers, suppliers and products, then the opening balances and the open items through import templates.
What moves from QAD to Sage X3?
| In QAD | In Sage X3 |
|---|---|
| GL accounts | General accounts |
| Sub-accounts, cost centers and projects | Analytical dimensions |
| Customers | Customers |
| Suppliers | Suppliers |
| Items and item-site data | Products |
| Bank accounts | Bank accounts |
Open items
Open customer and supplier invoices, open sales and purchase orders, scheduled orders, and inventory per site and location with its cost.
Open items load as customer and supplier open items with their original numbers, dates and due dates, so the aging in Sage X3 matches on day one.
History
QAD keeps posted GL transactions per entity and period. superglue reads every year the client wants to keep.
History loads as journal entries per period, account and dimension.
Which decisions do you make when you migrate from QAD to Sage X3?
- 01
Where do QAD sub-accounts and cost centers go?
QAD posts to an account, a sub-account, a cost center and a project. Sage X3 keeps the general account and records the other values as analytical dimensions.
superglue maps QAD accounts to general accounts, and the sub-accounts, cost centers and projects in use to dimension types.
- 02
Where do QAD item-site settings go?
QAD keeps planning, costing and inventory settings per item and site. Sage X3 keeps them per product and site, with stock locations inside each site.
superglue proposes a Sage X3 site for each QAD site, and product-site settings from each item-site record.
- 03
How many companies and sites does the client need?
In Sage X3, a company keeps the legal books, and sites hold the financial, sales, purchasing, inventory and production activity.
superglue recommends one company for each legal company in QAD, and a site for each location that keeps inventory or its own books.
- 04
Which analytical dimensions does the client need?
Sage X3 records analytical dimensions on journal lines, each account can require or default them, and the client chooses which dimension types to use.
superglue proposes dimension types from the segments and fields the client actually reports on.
- 05
Which cutover date does the client use?
A cutover on the first day of a period lets the open items and balances load as of one date. A fiscal year start keeps the year's reports and year-end filings in one system, and a date in the middle of the year means combining two systems for the audit and the tax returns. Avoid a date when the team must close the books or report results.
superglue recommends the first day of a month, and the first day of the fiscal year when the client can wait for it. The final balances load after the last period in QAD is closed.
- 06
How much history moves?
Most clients need the open items plus one to three years of monthly balances in Sage X3, at least the current and the prior fiscal year for comparison, and older years as yearly balances. The client keeps the older detail in an archive.
superglue recommends two years of monthly balances per account, and full transaction detail only where the client needs to look into single transactions.
What are the common challenges when you migrate from QAD to Sage X3?
Domains and entities are not the same
A QAD domain groups entities that share a base currency and a chart of accounts, and each entity keeps its own books. superglue maps each entity to a company in the new system and each domain's shared setup once.
Scheduled orders carry the customer's demand
Manufacturers ship against scheduled orders with releases from the customer's EDI. Decide early how releases arrive in the new system, because it changes the scope of the project.
Item-site settings override the item
QAD keeps planning, costing and inventory settings per item and per site, and site values override the item. superglue reads both and proposes the item settings for each site in the new system.
Standard costs can differ by site
QAD assigns cost sets to sites, so standard costs can differ by site. Agree which cost set the inventory value moves at before inventory moves.
Every object loads through its own import template
Sage X3 imports each object through an import template, with the same checks as manual entry, and the import log lists every record that fails. superglue builds the import files and explains every rejected record.
Customers and suppliers are business partners
Sage X3 keeps each trading partner once as a business partner, which can be a customer, a supplier or both. Agree with the client how duplicates across the old customer and vendor lists merge.
Activity codes switch features on
Sage X3 turns features and field sizes on with activity codes. Some are set when the folder is created, and every change needs a folder revalidation. Agree the activity codes in the design phase.
Open items must not count twice
Open invoices and bills post to the receivables and payables accounts when they load, and the opening trial balance holds the same amounts. Load the open items and the opening balances against one conversion account, and check that it ends at zero.
Plan fixed assets as their own stream
The trial balance brings the cost and the accumulated depreciation, but the asset register needs each asset with its in-service date, useful life and depreciation to date, and tax books need their own values. Agree early where the register lives after go-live, and reconcile it to the asset accounts.
superglue also runs the rest of the Sage X3 project. See the Sage X3 implementation
Frequently asked questions
Which data moves from QAD to Sage X3?
The chart of accounts, customers, vendors and items, the open items, and as much history as the client needs. The mapping table on this page shows where each record lands in Sage X3.
Does superglue write to Sage X3 without my approval?
No. superglue only reads QAD. Before any write to Sage X3, it shows the target, the connection and a transformed sample, and waits for your approval.
How do I know the migration is complete?
superglue reconciles the trial load and the final load against QAD: the trial balance per period, the open receivables and payables per customer and vendor, the uncleared bank items, and the inventory value. You get a reconciliation report to sign with the client.
What happens when I start this migration?
You sign up and connect the client's systems. If you want to see a full migration run first, superglue can set up Northwind Outdoor Supply, a sample client.
Start your QAD to Sage X3 migration
Sign up and connect the client's systems, or let superglue set up Northwind Outdoor Supply, a sample client, to see a full migration run first.