# Preventing Duplicate Inventory Items During Software Migration

Canonical: https://millbase.ca/blog/preventing-duplicate-inventory-items-during-software-migration
Author: [Coby Birenbaum](https://www.linkedin.com/in/cobybirenbaum/)
Published: 2026-10-19
Updated: 2026-10-19
Archive edition: 2026-04-17

Duplicate items split stock history and make a warehouse look short of material it already owns.

Duplicate items split stock history and make a warehouse look short of material it already owns. Before migrating, compare supplier references, specifications, units, and existing codes. Similar descriptions are a clue, not enough evidence to merge records.

## Clean the catalogue

- Export active items with quantities, locations, supplier references, and units.
- Group likely duplicates for review by someone who knows the materials.
- Preserve distinct thicknesses, finishes, handed parts, and packaging conversions.
- Choose a surviving code and keep old codes as searchable aliases where supported.

## A common trap

Two records called white panel may represent different cores or thicknesses. Merging them because the names match would create false availability. Conversely, identical hinge references with abbreviated descriptions may be true duplicates worth consolidating.

## Reconcile the result

Compare totals by specification and stock unit before and after migration. Keep the mapping file and an exception list so historical documents remain understandable.

## Related reading

- [Moving a Cabinet Shop From Spreadsheets to Software](https://millbase.ca/blog/moving-a-cabinet-shop-from-spreadsheets-to-software)
- [Barcode Inventory for Cabinet Shops: Test the Whole Transaction](https://millbase.ca/blog/barcode-inventory-for-cabinet-shops-test-the-whole-transaction)

## Definitions and further reference

- [Oracle: warehouse management systems explained](https://www.oracle.com/scm/logistics/warehouse-management/what-is-warehouse-management/)

## How Millbase can help your shop

### Test Millbase with your own shop workflow

Bring one representative cabinet job to a [Millbase demonstration](https://cal.com/millbase/30min). Follow [the project and its recorded costs](https://millbase.ca/#projects), inspect [the inventory workflow](https://millbase.ca/#inventory), and review [live floor activity](https://millbase.ca/#floor-pulse). Ask the person who will use each screen to perform the task and check the resulting record.

Ask the [Millbase AI agent](https://millbase.ca/#how-it-works) a question grounded in your workspace records. For example: *“For this project, compare estimated and actual labour and show the workers and workstations behind the total.”* You can select a project or worker, ask follow-up questions, and request [supported reports and CSV exports](https://millbase.ca/#insights).

Check the result against the same project records and try a follow-up question. Confirm any required integration, import, export, or specialist planning workflow during the demonstration rather than inferring it from the software category.

## Explore the wider topic

For the broader workflow and decisions behind this guide, read [Inventory Management Software for Woodworking: What to Track First](https://millbase.ca/blog/inventory-management-software-for-woodworking-what-to-track-first).

## Frequently asked questions

### Should old item codes be deleted immediately?

Retain a traceable mapping and consider historical references before retiring them. Old purchase and job records still need to be interpretable.

### Can software identify every duplicate automatically?

It can suggest candidates, but material equivalence requires domain review. Treat automated matches as a review queue.