The Quality Management Migration PowerTool (“Quality Module – Quality Inspector Migration Tool”)  is a Per-Tenant-Extension (PTE) that helps you migrate setup and transactional data between the Microsoft Quality Management extension and the Insight Works Quality Inspector app in the same company. Select Insight Works Quality Module – Quality Inspector Migration Tool to download the tool.

Using the migration tool helps you:

• Adopt Quality Inspector while preserving existing Quality Management templates and history (or the reverse).
• Avoid manual recreation of shared definitions (e.g., fields/tests, grades/results, templates, and generation rules).
• Run partial migrations (e.g., filters on templates, source configurations, or document sets) when you migrate in phases.

For Business Central partners and Quality Assurance Managers moving from Microsoft’s built-in Quality Management module to Quality Inspector, the Quality Management Upgrade PowerTool from Insight Works removes the rework. It migrates tests, templates, fields, grades, and lookup values between the two extensions automatically, inside the same company, in minutes rather than a rebuild project. Because Quality Management and Quality Inspector can run side by side with no dependency between them as long as there are not duplicated Business Central workflows, the migration can be run, checked, and run again before anyone commits to cutting over.

Important note on Business Central Workflows: If you have configured any Business Central workflows for Quality Management then you should disable them when enabling equivalents for Business Central Quality Inspector, this can help avoid equivalent automations from interfering with important automated processes.

Prerequisites

• Microsoft Quality Management and Insight Works Quality Inspector are installed.
• Insight Works Quality Module – Quality Inspector Migration Tool is installed (see above).
• Users who run migration have the Quality Management – Quality Inspector migration tool permission set.
  As a PTE, this tool is customizable to make it easier for consultants and resellers to migrate their custom data as needed. Source code for this PTE is available on request. You may need to renumber objects to work in the allowed object license range of your environment.
  Identification details of the Quality Module – Quality Inspector Migration Per-Tenant-Extension:
•  ID: 5a9f899e-bd69-4bac-a7aa-c3118d2cb8da
•  Name: Quality Module – Quality Inspector Migration Tool

Planning for Functional Differences

Quality Management is based on Insight Works Quality Inspector, however the objects were renumbered and renamed and functionality forked from a specific point in time.  Quality Inspector continue to evolve it’s functional and technical capabilities, and also has more built-in integration with other apps in the Insight Works ecosystem.

It’s important to be aware of the differences between Quality Management and Quality Inspector when migrating between the two, there are some capabilities in Insight Works Quality Inspector that do not exist in the Microsoft provided Quality Management.

A functional overview of the differences can be found here: https://dmsiworks.com/quality-inspector-vs-microsoft-quality-management

More technical differences and Terminology Differences can be found here : https://kb.dmsiworks.com/knowledge-base/quality-inspector-and-the-microsoft-quality-management-extension/

Planning Your Migration When You Have Customized Report Layouts (either Word or RDL, either for printing or for PDF)

The migration tool does not migrate report layouts.

If you have customized your report layouts for things like your CoA (Certificate of Analysis), Inspection Results, FAIR Form 3, NCR Reports, or any other printable or PDF reports then you must plan to re-create those custom report layouts in the other tool.

Quality Inspector uses a different object range than Microsoft’s Quality Management solution, and in some cases the data items also differ.

Several enhancements to the Certificate of Analysis (COA) functionality and Non-Conformance Reports (NCRs) also exist in Quality Inspector that are absent in Quality Management.  Some reports, such as the FAIR Form 3 only exist in Quality Inspector.

Migration Tools

The migration configuration reports will migrate Quality Management / Quality Inspector Setup, source configurations, and templates you include in the report filters. As each template is processed, the tool adds generation rules, Quality Management tests / Quality Inspector fields, Quality Management inspection results / Quality Inspector grades, lookup codes, and grade condition configurations those templates need.

Tests / inspections reports migrate documents only (Quality Inspector tests or Quality Management inspections). They do not refresh existing configuration unless a test line references something missing, and then the tool climbs and inserts what is needed (see below).

These tools include the Migrate even if already migrated option. Leave it disabled to only insert rows not already on the target; enable it when you want to intentionally re-sync the already copied configuration.

Dependency climbing (automatic prerequisites)

When you migrate a template or a test/inspection document, the tool does not assume every related row was previously migrated. It walks dependencies and creates missing target records, so references stay valid:

• Fields / Tests: Template lines and document lines reference fields (Quality Inspector) or tests (Quality Management). Those definitions are migrated when missing (including field-scoped grade condition rows where applicable).
• Grades / Inspection results: Grade/result codes trigger migration of the corresponding grade (Quality Inspector) or inspection result (Quality Management) if it does not exist yet.
• Lookup tables: If a field uses the product’s lookup value table, the tool migrates lookup codes / test lookup values that match that field’s filter.
• Templates from documents: Templates are ensured on the target (insert-only when climbing from document migration) so template lines can align with inspection/test lines.
• Generation rules: Migrating a template brings across generation rules for that template code.

Migrate from Quality Management to Quality Inspector

1. Plan the scope:
   1. Decide whether you need full configuration or only templates/source configurations you select, and whether you should move historic inspections or only a subset (e.g., filters on number, re-inspection, status, template).
2. Run configuration migration:
   1. Navigate to the Migrate Quality Management Configuration to Quality Inspector report request page.
   2. Set Migrate even if already migrated to resync (optional).
   3. Set filters  as needed (if you only want certain source configurations or templates).
   4. Run the report and review the completion message (setup, source configurations, and templates).
3.  Run inspection migration (documents):
   1. Navigate to the Migrate Quality Management Inspections to Quality Inspector report request page.
   2. Filter Qlty. Inspection Header as needed (optional).
   3. Run the report (missing templates, fields, grades, lookups, and generation rules required by those inspections are added automatically where possible; existing, unreferenced Quality Inspector configuration remains unchanged).
4.  Handle what the tool does not migrate:
   1. Revisit workflows, Quality Inspector-only setup fields, and any field types that have no Quality Management equivalent.

Migrate from Quality Inspector to Quality Management

1. Plan the scope:
   1. Decide whether you need full configuration or only templates/source configurations you select, and whether you should move historic inspections or only a subset (filters on number, re-inspection, status, template).
2. Resolve mapping limits before migration:
   1. Quality Inspector setup must use Production trigger and Picture upload values that map to Quality Management. Templates used with AQL-style sample sources cannot map to Quality Management until you change the sample source for the template on Quality Inspector. Field types such as Numeric Expression or Signature have no Quality Management test value equivalent; correct or remove those references before migrating to Quality Management.
3. Run configuration migration:
   1. Navigate to the Migrate Quality Inspector Configuration to Quality Management report request page.
   2. Enable Migrate even if already migrated for a full refresh of already-copied setup rows (optional).
   3. Filter source configurations and/or templates if you do not need the full set.
   4. Run the report and confirm the summary.
4.  Run test migration (documents):
   1. Navigate to the Migrate Quality Inspector Tests to Quality Management report request page.
   2. Filter IWX QI Test as needed.
   3. Run the report (the tool climbs dependencies — templates, fields, grades, lookups, generation rules — for those tests; existing, unreferenced Quality Management configuration remains as is.

Notes and best practices

• Run the Assisted Setup for the target product to ensure base configuration (e.g., default No. Series) has been generated.
• Run configuration migration first for a clean baseline, then tests/inspections for history, or rely on climbing from document-only runs if your scope is narrow.
• Use Migrate even if already migrated only when you intend to overwrite existing target configuration from the source.

Troubleshooting “A response with description … already exists”

If you get an error with “A response with description ABC already exists”, such as “A response with description Create an Internal Put-away already exists” (the response could be different) this could occur in some specific versions and sequence of events even after the Microsoft Quality Management module is un-installed.  Because the Microsoft Quality Management module is based on the Insight Works Quality Inspector it maintains some of the names both Insight Works Quality Inspector and Microsoft Quality Management have either the same or similar workflow response names.  The Business Central workflow management system however maintains the response names even after the uninstall.  Insight Works attempts to work around this by detecting this scenario and then suffixing it’s own responses in this scenario with ‘IW’ or ‘IWX’.

To resolve this error caused by the duplicate responses manually, after un-installing Microsoft Quality Management perform these steps:

1. Remove any workflows build with Microsoft Quality Management first. If you have Quality Management workflows and have already un-installed Microsoft Quality Management then temporarily re-install it first to remove the workflows without error.
2. After any Quality Management workflows are removed un-install Microsoft Quality Management.
3. Create a configuration package
4. Add table 1521 (workflow response)
5. Add table 1520 (workflow event)
6. Export to excel
7. In excel, delete the rows with QLTY as a prefix from both tables. This prefix is used by the Microsoft Quality Management module.
8. Import the excel file
9. Enable ‘delete table records before processing’
10. Apply Package
11. Install Quality Inspector
12. Navigate back to workflows to register the Quality Inspection events