QAD Adaptive ERP Migration Readiness Assessment
Moving from QAD Enterprise Edition to QAD Adaptive ERP is rarely blocked by the standard product. It is slowed by custom code, undocumented interfaces and unowned data. This ten question assessment shows where your site stands and what to fix before you commit a timeline.
1. How many custom programs (.p, .w, .i) are in production use beyond the standard QAD code?
Count only what users actually run, not dead code left from past projects.
2. Are your customizations documented with purpose, owner and the standard program they touch?
3. How are your external systems connected to QAD today?
Examples: EDI, WMS, MES, CRM, banks, shipping, tax engines.
4. How current is the version you run today relative to the version your target Adaptive ERP release expects?
5. What is the state of your master data (items, BOMs, routings, customers, suppliers)?
6. How many reports, browses and dashboards do users depend on that are custom or built outside QAD?
7. Do you have a test environment that mirrors production data and integrations?
8. How well do you understand which standard processes you would change versus keep as-is?
9. Do you have named business owners and key-user time committed for testing?
10. How do you handle compliance and audit evidence (traceability, e-signatures, tax, export controls)?
How to use this assessment
Answer for your production environment as it runs today, not as you wish it did. Involve at least one person from IT, one from finance and one from operations, because each sees different gaps. The score is a percentage of the maximum, and the band tells you whether to assess further, close gaps, plan, or execute. Export the result to PDF to share with a steering group.
- Answer from evidence, not memory
- Let different roles answer different questions
- Re-run the assessment after each gap-closing step
- Treat unknown as the lowest answer
What the questions measure
The questions cover five areas that decide migration effort: customization volume and documentation, integration approach, data quality, reporting dependence and organisational readiness. Customizations carry the most weight because each one needs a decision: retire, replace with standard behavior, or rebuild on the newer architecture. Integrations come next because they connect your plant, suppliers and banks and are often discovered late.
Reading your band
A low band does not mean you should not migrate. It means the cost of discovery is still ahead of you and will land in the project if you do not do it first. A high band means the remaining risk is execution: cutover, testing time and user adoption. In either case, write down what you will do for each recommendation and assign an owner.
Common mistakes
Teams often count customizations by file rather than by business function, which hides how many processes depend on them. Another mistake is treating reports as an afterthought; users judge a new system by whether their daily reports still exist. Finally, many sites plan data migration once. Plan at least two rehearsals, and compare balances, open orders and inventory by location between source and target.
- Counting files instead of business functions
- Ignoring custom reports and browses
- One data migration attempt instead of rehearsals
- No protected time for key users
Frequently Asked Questions
Is this the same as a QAD fit-gap?
No. This is a readiness screen. It tells you whether you have the inputs to run a fit-gap and plan a migration. A fit-gap goes process by process and decides what to change. Use this first, then run the fit-gap with process owners.
Does a low score mean we should stay on QAD EE?
Not necessarily. It means you do not yet know the cost of moving. Many low scores come from missing documentation, which can be fixed in weeks. Staying put has its own risks around support, security patching and talent, so decide with data from the inventory.
Who should fill this in?
Ideally the QAD administrator, a finance lead, an operations lead and whoever owns integrations. If one person answers alone, you will usually score yourself too high on areas outside their daily work.
Is my data sent anywhere?
The assessment runs in your browser. Your answers stay on your device unless you choose to request a review. Exporting to PDF is generated locally.
If you want a second pair of eyes on your customization and interface inventory, Netray can review it and show where AI-assisted analysis speeds up the work.
Related Tools
QAD EE to Adaptive ERP Migration Checklist
A grouped checklist for planning and executing a move from QAD Enterprise Edition to Adaptive ERP, from inventory to hypercare.
Other ERPsQAD Menu Program Reference Worksheet
An editable QAD menu and program reference you fill in once and export to Excel, with usage and risk columns for training, access reviews and migration planning.
ERP OperationsIFS Cloud Upgrade Test Checklist
A grouped test checklist for IFS release updates and upgrades covering environments, core processes, integrations, reports, security and sign-off.
More ERP Migration & Selection tools
See all- ERP TCO Comparison Calculator (5-Year)
- ERP Migration Risk Assessment
- Data Migration Effort Calculator
- ERP Selection Scorecard for Manufacturers
- ERP Go-Live Readiness Checklist
- ERP Change Management Readiness Assessment
- ERP Integration Complexity Calculator
- Cloud vs On-Premise ERP Cost Calculator
- ERP Upgrade vs Replace Assessment
New to QAD? Start with the QAD guide and toolkit.
Keep exploring
Free tools
- QAD EE to Adaptive ERP Migration ChecklistA grouped checklist for planning and executing a move from QAD Enterprise Edition to Adaptive ERP, from inventory to hypercare.
- QAD Customization Migration Effort CalculatorSize the work to carry QAD customizations forward: count them by complexity, set the share you can retire, add testing and contingency.
- QAD EE Custom Code Inventory WorksheetEditable inventory of QAD customizations with type, use, complexity and retire or rebuild decision, totalling rebuild effort.
ERP fixes and how-tos
- QAD vs Plex: Which Fits a Discrete Manufacturer?QAD or Plex for a discrete manufacturer? A practical comparison of architecture, shop floor depth, cloud model, customisation, data access, and migration risk.
- QAD ERP Software Implementation: Steps, Environments and Knowledge BaseQAD ERP implementation phases, what the test, development and production environments are for, and where to find QAD knowledge base and documentation.
- QAD ERP Tables and API Access: Key Tables, SQL and Integration OptionsKey QAD ERP tables such as pt_mstr and so_mstr, how to query them via OpenEdge SQL, and which API options exist for integration. Read-only guidance.
AI on your ERP
- AI for QAD Adaptive ERP in automotive and industrial manufacturingAdd AI to QAD Adaptive ERP or Enterprise Edition for automotive and industrial manufacturing, grounded on QXtend and QAD's API layer, on-prem or private cloud.
- AI for QAD Supply Chain: Schedules, Suppliers and MRP ExceptionsAI for QAD supply chain: scheduled order review, supplier delivery risk, MRP exceptions and inventory questions over QAD data, private and on-prem capable.
Integrations
- How to use ChatGPT with QAD Adaptive ERPHow to use ChatGPT with QAD: exports versus live API access, custom GPT actions, enterprise data controls and when a private model is the safer choice.
- How to connect Claude to QAD Adaptive ERPConnect Claude to QAD through an MCP connector, use Anthropic API, AWS Bedrock or Vertex, or go on-prem with open models when QAD data must stay inside.