How to Migrate Data to a New ERP System

ERP data migration is not just uploading Excel files.

It is the process of deciding what data is worth carrying forward, cleaning it, structuring it, testing it, and validating that the new ERP can run the business from day one.

Many ERP projects become painful because data migration is treated as a technical task. Someone exports old data, someone formats a sheet, someone uploads it, and everyone hopes the reports will be correct.

That is risky.

For a small manufacturing business, data migration affects everything:

• Item masters
• Units of measure
• Customers
• Suppliers
• BOMs
• Opening stock
• Pending sales orders
• Pending purchase orders
• WIP
• Finished goods
• Price lists
• Tax details
• User roles
• Reports

If this data is wrong, users lose trust quickly.

The ERP may be good, but the business will say, “The system is wrong.” Often, the system is only showing messy data more clearly.

Start with a Migration Scope

Do not migrate everything just because it exists.

Start by deciding what the new ERP needs for go-live.

A practical phase-one migration scope for manufacturers may include:

• Active customers
• Active suppliers
• Active item masters
• Units of measure
• Product groups
• BOMs for active products
• Opening stock
• Open sales orders
• Open purchase orders
• Open production orders or WIP
• Finished goods stock
• User list and roles
• Essential price lists
• Tax fields

Historical data can often be archived separately.

Trying to migrate years of old transactions into a new ERP can increase cost, delay, and errors. Sometimes it is better to keep old records in read-only format and bring only active operational data into ERP.

Clean Item Masters First

Item master cleanup is usually the hardest and most important migration task.

Manufacturing businesses often have duplicate and inconsistent item names.

Examples:

• MS Sheet 2mm
• M.S. Sheet 2 MM
• Mild Steel Sheet 2mm
• MS SHEET-2

These may refer to the same material, but the ERP will treat them as separate items unless cleaned.

Before migration, define:

• Item code
• Item name
• Item group
• Unit of measure
• Purchase item or manufactured item
• Raw material or finished good
• Active or inactive status
• Tax classification where relevant
• Minimum stock if needed
• Storage location if needed

Clean item masters create cleaner inventory, purchase, production, and reports.

Standardize Units of Measure

Unit of measure mistakes create major ERP problems.

If one sheet uses kg, another uses grams, and another uses pieces, the system may calculate wrong stock or wrong material requirement.

Before migration, standardize:

• Purchase unit
• Stock unit
• Production consumption unit
• Sales unit
• Conversion factors

For example, material may be purchased in kg but consumed in pieces or meters. This must be defined clearly.

Unit conversion should not be guessed during upload.

Clean Customer and Supplier Data

Customer and supplier masters should be cleaned before migration.

Remove inactive or duplicate records where possible. Standardize names, addresses, tax numbers, contact details, and payment terms.

Customer data should include:

• Customer name
• Billing address
• Shipping address
• Contact person
• Phone number
• Email
• GSTIN or tax details where applicable
• Credit terms if used

Supplier data should include:

• Supplier name
• Address
• Contact person
• Tax details
• Payment terms
• Item relationships if needed

Clean customer and supplier records reduce billing, purchase, and reporting confusion.

Prepare BOMs Carefully

For manufacturers, BOM migration is critical.

A wrong BOM can create wrong purchase requirements, wrong production planning, wrong costing, and wrong inventory consumption.

Before uploading BOMs, verify:

• Finished product code
• Raw material codes
• Quantity per unit
• Unit of measure
• Scrap or wastage allowance
• Alternate material rules if any
• Version or revision where relevant
• Active and inactive BOMs

If BOMs are outdated, do not migrate them blindly.

Use migration as a chance to clean product structure.

Verify Opening Stock Physically

Opening stock is one of the most sensitive migration areas.

If opening stock is wrong, users will distrust ERP from day one.

Before go-live, conduct a physical stock check and prepare opening balances by:

• Item
• Location
• Batch or lot if needed
• Stock status: available, rejected, QC hold, WIP, finished goods
• Unit of measure
• Value if required

Do not upload old stock numbers without verification.

A clean opening stock gives the new ERP a fair start.

Decide What to Do with Pending Orders

Open transactions matter more than old history.

Prepare lists of:

• Pending sales orders
• Pending purchase orders
• Open production orders
• WIP jobs
• Pending dispatches
• Open invoices if relevant
• Customer advances if relevant
• Supplier advances if relevant

These records allow the business to continue operations after go-live.

If pending orders are missing, teams will need parallel Excel sheets, which weakens ERP adoption.

Do Not Migrate Bad History Without Purpose

Many businesses want all historical transactions inside the new ERP.

That can be expensive and risky.

Ask:

• Do we need transaction history for daily operations?
• Can old data stay in the old system or archive?
• Do we need only balances and open transactions?
• Which reports require historical data?
• Is old data clean enough to migrate?

For many small businesses, active masters, opening balances, and open transactions are enough for go-live.

Historical records can be kept separately for reference.

Use Templates and Validation

ERP vendors usually provide data templates.

Use them carefully.

Each template should have clear columns, required fields, allowed values, and examples.

Before final upload:

• Check mandatory fields
• Remove duplicates
• Validate item codes
• Validate units
• Match BOM item codes with item master
• Match customer and supplier codes
• Check tax fields
• Check stock quantities
• Check negative values
• Review inactive records

A small validation effort before upload prevents many go-live problems.

Test Migration Before Final Go-Live

Never migrate directly into final go-live without testing.

Do at least one trial migration.

After trial upload, test:

• Can users find items?
• Are BOMs correct?
• Does stock show properly?
• Can sales orders be created?
• Can purchase orders be created?
• Can production orders be created?
• Do reports look reasonable?
• Are customer and supplier details correct?
• Are permissions working?

Trial migration reveals formatting and process issues early.

Assign Data Owners

Data migration cannot be owned only by IT or the ERP vendor.

Each area needs a business owner:

• Item master: stores or production
• BOM: production or engineering
• Customers: sales or accounts
• Suppliers: purchase or accounts
• Stock: stores
• Pending orders: sales and purchase
• Tax fields: accounts
• User roles: management

These people must validate the data before go-live.

If nobody owns the data, errors become everyone’s problem later.

Plan the Cutover

Cutover is the point where the business stops using old operational records and starts using the new ERP.

A cutover plan should define:

• Final transaction date in old system
• Physical stock verification date
• Final data extraction date
• Final migration upload
• Validation responsibility
• Go-live date
• Old system access plan
• Excel tracker retirement plan
• Support window

Cutover must be planned, not improvised.

Where AICAN Optiwise Fits

AICAN Optiwise can help manufacturers migrate into a practical ERP structure across inventory, purchase, production, sales, dispatch, quality, and reports. The migration conversation should begin with the data needed to run these workflows properly.

The AICAN team can help businesses identify which data should be migrated, which should be cleaned, and which old records can remain archived. This keeps implementation focused and reduces the risk of carrying old confusion into the new system.

For manufacturers moving from Excel, accounting software, or older ERP systems, Optiwise migration should prioritize clean item masters, BOMs, stock, customers, suppliers, and open transactions.

You can learn more about AICAN on the About AICAN page.

FAQ

What data should be migrated to a new ERP?

Most businesses should migrate active masters, opening balances, open sales orders, open purchase orders, active BOMs, current stock, user roles, and essential operational data.

Should I migrate all historical data?

Not always. Historical data can often stay in the old system or archive. Migrating bad history can increase cost and errors.

What is the biggest ERP migration mistake?

The biggest mistake is uploading messy data without cleanup and validation. Bad item masters, BOMs, and opening stock damage trust quickly.

Who should validate migrated data?

Business users should validate data. Stores, production, sales, purchase, accounts, and management should each validate their areas.

How many trial migrations are needed?

At least one trial migration is strongly recommended. Complex businesses may need multiple rounds.

Why is opening stock important?

Opening stock affects inventory trust from day one. If opening stock is wrong, users will continue checking manually and ERP adoption will suffer.

Founder’s Note

Data migration is where old habits try to enter the new system.

At AICAN, we believe migration should be treated as a cleanup opportunity, not only a transfer activity. If your old item names, BOMs, stock, and customer records are messy, ERP will not magically fix them after upload.

A clean start gives the system and the team a better chance.

Final Thought

Migrating data to a new ERP is about judgment.

Bring what is useful. Clean what is messy. Archive what is old. Validate what matters. If the data is prepared properly, the ERP starts with trust instead of doubt.