---
title: "Migrate Between Quality Management and Quality Inspector"
app: "Quality Inspector"
section: "How-to guides"
last_updated: "2026-10-30"
url: "https://insight-works.com/kb/quality-inspector/migrate-between-quality-management-and-quality-inspector/"
---

# Migrate Between Quality Management and Quality Inspector

The Quality Management Upgrade PowerTool is an Insight Works application that migrates setup and transactional data between the Microsoft Quality Management extension and the Insight Works Quality Inspector extension in the same company. Install it from Microsoft AppSource (Marketplace). It is no longer distributed as a per-tenant extension (PTE).

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 a full Quality Management to Quality Inspector cutover from Assisted Setup or run partial migrations from the migration reports (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, within 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.

 Note: If you have configured any Business Central workflows for Quality Management, disable them when enabling equivalents for Business Central Quality Inspector; this helps avoid equivalent automations from interfering with important automated processes.

### Prerequisites

- Business Central version 28 (2026 release wave 1) or newer.
- Microsoft Quality Management and Insight Works Quality Inspector (version 7.27 or newer) are installed.
- Insight Works Quality Management Upgrade PowerTool is installed.
- Users who run migration have the Quality Management Upgrade PowerTool permission set.

If you previously installed the PTE named Quality Module – Quality Inspector Migration Tool (ID 5a9f899e-bd69-4bac-a7aa-c3118d2cb8da), uninstall the extension before using the Quality Management Upgrade PowerTool. Do not keep both installed.

### Planning for Functional Differences

Quality Management is based on Insight Works Quality Inspector; however, the objects were renumbered and renamed, and the functionality forked from a specific point in time. Quality Inspector continues to evolve its 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.

For more information on a functional overview of the differences, see the [_Quality Inspector vs. Microsoft Quality Management_](https://dmsiworks.com/quality-inspector-vs-microsoft-quality-management) page.

For more technical differences and Terminology Differences, see the [_Quality Inspector and the Microsoft Quality Management Extension_](/kb/quality-inspector/quality-inspector-and-the-microsoft-quality-management-extension/) page.

### 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.

Plan to re-create custom report layouts in the other tool if you have customized your report layouts for:

- CoA (Certificate of Analysis)
- Inspection Results
- FAIR Form 3
- NCR Reports
- Any other printable or PDF reports

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.

### Ways to Run the Migration

There are two ways to run the tool:

#### Assisted Setup wizard (recommended for a full move from Quality Management to Quality Inspector)

1. Open **Assisted Setup** and select **Upgrade Quality Management to Quality Inspector** (short title: **Upgrade QM to QI**).
2. Follow the instructions. The wizard first migrates configuration (setup, source configurations, and templates), then inspection documents.
3. Select **Migrate even if already migrated** if you want to refresh the Quality Inspector configuration that was already copied.
4. Select **Upgrade**.

The wizard does not show report request pages and does not apply filters. It migrates the full configuration and all inspections in the company. Missing tests, results, generation rules, and lookup values are added automatically as each template or inspection requires them. The existing Quality Inspector configuration is left unchanged unless you select **Migrate even if already migrated**.

#### Reports (filtered or phased migration)

Use the _Upgrade Quality Management Configuration to Quality Inspector and Upgrade Quality Management Inspections to Quality Inspector_ reports when you need filters, a configuration-only run, or inspections/tests only.

### Migration Tools

The migration configuration reports migrate Quality Management 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.

 Note: If a test line references a template line that cannot be matched on the target (template + line + field/test code), migration stops with an error until the template is corrected.

### Migrate from Quality Management to Quality Inspector

1. Plan the scope:

   1. Decide whether you need a full, unfiltered cutover (Assisted Setup) or only selected templates, source configurations, or historic inspections (migration reports with filters on number, re-inspection, status, and template).
2. Complete one of the following:

   - Full company migration:

      1. Open **Assisted Setup** / **Upgrade Quality Management to Quality Inspector**.
      2. Set **Migrate even if already migrated** if needed.
      3. Select **Upgrade**.
   - Filtered configuration run:

      1. Navigate to the _Upgrade 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. Navigate to the _Upgrade Quality Management Inspections to Quality Inspector_ and run inspection migration (documents), unless the wizard already did this.
4. Handle what the tool does not migrate:

   - Revisit workflows, Quality Inspector-only setup fields, and any field types that have no Quality Management equivalent.
   - Re-create customized report layouts in Quality Inspector.

1.

### Notes and best practices

- Run the Assisted Setup for the target product to ensure base configuration (e.g., default No. Series) has been generated.
- For a typical Quality Management to Quality Inspector cutover, use the _Upgrade Quality Management to Quality Inspector_ Assisted Setup wizard.
- For a filtered or phased move, 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.
- After cutover, you can uninstall the Quality Management Upgrade PowerTool. It is a migration helper, not a runtime dependency of Quality Inspector.

### Troubleshooting “A response with description … already exists”

If you get an error with “A response with description [xxx] already exists” (e.g., A response with description Create an Internal Put-away already exists), this may occur in 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). However, the Business Central workflow management system maintains the response names even after the uninstall. Insight Works attempts to work around this by detecting this scenario and then suffixing its own responses in this scenario with ‘IW’ or ‘IWX’.

Uninstall Microsoft Quality Management and resolve this error caused by the duplicate responses by completing the following:

For the scenarios of migrating to Quality Inspector after un-installing Microsoft Quality Management.

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