A successful migration starts long before you click "Export." The goal is not just to move data, but to ensure the source file is internally consistent, free of corruption, and structured in a way the destination system can accept.
For a manufacturing company with 10 years of history, customers, vendors, and inventory assemblies, the most important mindset is: treat the migration like a data quality project, not just a software conversion.
1. Decide what historical data actually needs to move
Before cleaning anything, determine whether you'll migrate:
- Full transactional history (10 years)
- Opening balances plus a few years of history
- Master records only (customers, vendors, items) with historical reports archived separately
Many organizations keep older years in a read-only QuickBooks Desktop file while migrating only recent years into the new ERP. This can reduce migration complexity dramatically.
2. Create multiple verified backups
Before making any changes:
- Create a full QuickBooks backup (.QBB)
- Create a portable company file (.QBM)
- Copy the original company file to secure storage
- Keep one completely untouched backup
This allows you to restart if cleaning introduces unexpected problems.
3. Update QuickBooks Desktop
Run the latest release of your version of QuickBooks Desktop Enterprise.
Many migration utilities expect the latest maintenance updates, and Intuit has fixed numerous data integrity issues over the years.
4. Run Verify Data and Rebuild Data
This is probably the single most important technical step.
Run:
- File → Utilities → Verify Data
If errors appear:
- File → Utilities → Rebuild Data
Then run Verify again.
Repeat until Verify reports no remaining problems.
If Verify continues reporting unresolved errors, those should be corrected before migration because they often become much harder to fix afterward.
5. Resolve list integrity issues
Review every major master list.
Customers
Look for:
- Duplicate customers
- Inactive duplicates
- Incorrect parent/child relationships
- Missing addresses
- Missing tax information
- Invalid email addresses
Vendors
Check for:
- Duplicate vendors
- Inconsistent naming
- Missing tax IDs (if applicable)
- Inactive duplicates
Employees
Ensure:
- Names are consistent
- Inactive employees are correctly marked
- Payroll data is complete if payroll history is migrating
Chart of Accounts
Review for:
- Duplicate accounts
- Unused accounts
- Incorrect account types
- Improper parent/subaccount structure
6. Clean inventory data
Manufacturing inventory is often the most difficult part of migration.
Review:
- Negative inventory quantities
- Items with zero cost but positive quantity
- Items with incorrect units of measure
- Obsolete inventory
- Duplicate SKUs
- Missing preferred vendors
If using:
- Assemblies
- Bills of Materials
- Multiple warehouses
- Lot tracking
- Serial numbers
Document exactly how these features map into the destination system because they rarely transfer one-to-one.
7. Review assembly items carefully
For manufacturing companies this deserves special attention.
Check every assembly for:
- Missing components
- Incorrect quantities
- Obsolete parts
- Inactive components still referenced
- Incorrect costs
NetSuite, in particular, may require different BOM structures than QuickBooks Desktop.
8. Close old accounting periods
Ensure:
- All reconciliations are complete
- Prior-year adjustments are finalized
- Financial statements are approved
Avoid migrating while previous periods are still changing.
9. Reconcile every balance sheet account
Before migration, reconcile:
- Bank accounts
- Credit cards
- Loans
- Accounts Receivable
- Accounts Payable
- Payroll liabilities
- Inventory Asset
Your balances should agree with external records.
10. Review Accounts Receivable
Look for:
- Old unapplied payments
- Negative balances
- Duplicate invoices
- Credits without applications
- Customers with incorrect balances
11. Review Accounts Payable
Similarly, clean:
- Duplicate bills
- Vendor credits
- Unapplied payments
- Negative balances
- Old outstanding checks
12. Remove or merge duplicates where appropriate
Examples include:
- Duplicate customers
- Duplicate vendors
- Duplicate inventory items
- Duplicate classes
- Duplicate terms
Do this carefully because merges cannot easily be undone.
13. Standardize naming conventions
Inconsistent names create reporting problems later.
Examples:
Instead of:
- ABC Inc
- A.B.C.
- ABC Incorporated
choose one standard.
Likewise for:
- Items
- Vendors
- Customers
- Classes
- Departments
14. Review custom fields
Inventory companies often have custom fields like:
- Color
- Size
- Revision
- Drawing Number
- Engineering Change Level
Document:
- Every custom field
- Where it is used
- Which destination field it maps to
15. Review inactive records
Decide whether to migrate:
- Inactive customers
- Inactive vendors
- Inactive inventory
- Inactive employees
Many organizations reduce migration complexity by leaving obsolete records behind.
16. Document workflows
Don't focus only on data.
Document processes such as:
- Sales orders
- Purchase orders
- Manufacturing builds
- Inventory adjustments
- Receiving
- Shipping
- Job costing
Cloud ERPs often handle these workflows differently.
17. Produce baseline financial reports
Generate and save reports immediately before migration, including:
- Balance Sheet
- Profit & Loss
- Trial Balance
- General Ledger
- Inventory Valuation Summary
- Inventory Stock Status
- A/R Aging
- A/P Aging
These become your validation benchmarks after import.
18. Test the migration with a copy
Never migrate the production file first.
Instead:
- Copy the company file.
- Perform a trial migration.
- Compare:
- Trial Balance
- Inventory valuation
- Customer counts
- Vendor counts
- Open invoices
- Open purchase orders
- Inventory quantities
- Assembly structures
Repeat until the results are acceptable.
19. Understand platform-specific limitations
Be aware that QuickBooks Online and NetSuite differ significantly from QuickBooks Desktop:
| Area | QuickBooks Online | NetSuite |
|---|
| Inventory Assemblies | Limited compared to Desktop | Much more sophisticated but requires mapping |
| Manufacturing | Basic | Extensive manufacturing capabilities |
| Custom fields | Limited | Highly customizable |
| Historical transactions | May have import limitations | Usually handled through specialized migration tools |
| Multi-location inventory | Supported with different behavior | Robust but different architecture |
20. Build a migration checklist with sign-offs
Create a checklist covering:
- Data verification complete
- Backup completed
- Verify/Rebuild successful
- Reconciliations complete
- Inventory validated
- BOMs validated
- Financial reports saved
- Test migration approved
- Final migration scheduled
- Post-migration validation completed
Assign an owner and sign-off for each task to reduce the risk of missing critical steps.
A note on migration strategy
For a manufacturing business with a decade of history and complex inventory assemblies, an incremental, tested migration is generally lower risk than a "big bang" approach. Performing at least one full trial migration and validating financial statements, inventory quantities and values, and open transactions against your QuickBooks Desktop reports before the production cutover can uncover mapping issues while they're still easy to correct. This approach is especially important when moving to NetSuite, where manufacturing and inventory capabilities are more comprehensive than those in QuickBooks Desktop and typically require careful configuration rather than a direct one-to-one import.
