ERP Data Migration for Manufacturing: A Pilot Import and Stock Reconciliation
Move item masters, BOMs, stock and open orders into Optiwise. Use our pilot-migration workbook to map fields, resolve rejected rows and reconcile opening stock.

Move your factory to Optiwise with the records your team needs to run the next order: consistent items and units, the current bill of materials, usable opening stock and the balance on open purchases and sales. Start with a small pilot, fix the source errors and reconcile the quantities before moving the rest. We charge ₹0 for implementation; your subscription, optional add-ons and IoT hardware are separate.
Download the pilot-migration workbook
Download the editable ERP migration workbook. It includes a field-mapping sheet, a rejected-row log and an opening-stock reconciliation. The examples are illustrative. Use it to prepare your data with our implementation team; it is not a file to upload directly into an Optiwise importer.
Start with one product you can follow through the factory
Choose a finished product with a current drawing, a bill of materials (BOM), one open customer requirement and a material you buy. Include its supplier, store, unit and any batch or lot identity. Add a partially received purchase order so the pilot covers an exception your buyers and stores team already handle.
Your item owner agrees the codes and units. Planning owns the current BOM and route. Stores owns counted opening quantities and quality identifies material still under inspection. Purchasing and sales confirm what remains open. Keep each old record ID beside its new reference so you can trace a mismatch back to the source.
Map the relationships before importing quantities
| Record | Carry into the pilot | Check before proceeding |
|---|---|---|
| Item and unit | Item code, description, base unit and conversion | Two names must not create two copies of the same item. |
| BOM and route | Finished item, basis quantity, components, process sequence and drawing | Each component resolves to the intended item and unit. |
| Opening stock | Item, store, quantity, tracking identity and quality status | Counted stock and usable stock are distinguishable. |
| Open orders | Old document reference, party, item and remaining quantity | Previously received or dispatched quantities are not imported again as new demand. |
A supplier buying unit of one box cannot become one piece unless the agreed conversion supports it. If your old system uses flat item IDs and you want variants in Optiwise, agree that mapping before loading transactions. A changed name alone does not resolve the relationship.
Resolve rejected rows without losing the source
Keep the source file and row number, the field that failed, the reason, the person correcting it and the retry result. For example, a component referring to an unknown item needs its item mapping resolved before the BOM can use it. A missing unit conversion needs a business answer; replacing it with 1 would create a different quantity.
Correct the source and retry the affected pilot records. Record the resulting ID and result in the log. Import mechanisms and required fields depend on the records being moved, so we agree the actual format during setup rather than treating a general worksheet as a universal upload file.
Reconcile opening stock and open balances
Use a clear cutover time. Your stores team counts the item in each location and records movements after that time separately. Compare the expected quantity in the new system with the quantity actually loaded for the same item, store, unit and quality status. Investigate a difference before changing either balance.
For an illustrative purchase of 100 pieces, 75 have arrived: 70 were accepted and five rejected. If all 100 are still needed, 25 have not arrived and five require a return or replacement decision. Keep those states distinct; loading the original 100 as a new open requirement would lose the receipt history and overstate the work still to do.
For a BOM requiring two pieces per finished unit, a 50-unit pilot needs 100 pieces before scrap allowances or other configured requirements. Check that calculation against the source BOM. Then follow a receipt, inspection, issue, process entry and accepted finished-goods receipt in our production workflow. Keep the stock movement visible in inventory and the open balance in purchasing.
Cut over when the pilot records agree
Keep the old system available for historical reference, agree the final movement cutoff and repeat the reconciliation after the full load. Your business owners accept the opening quantities, current documents and open balances. Our setup work connects those records to the roles, forms and workflow rules your factory will use.
For another documented import approach, ERPNext's Data Import guide explains template-based imports and error handling. Optiwise's pilot should use the format agreed for your own records.
Questions about moving manufacturing data
What should we migrate first?
Start with the organisation, users, item and party masters, units and stores. Use a small linked BOM, opening-stock and open-order pilot before the full load.
Does implementation cost extra?
Optiwise implementation costs ₹0. Subscription prices, optional add-ons and IoT hardware are separate.
Should rejected or quality-held stock be treated as available?
Keep its status separate. Mandatory inspection can block stocking until the requirement is satisfied; optional inspection follows a different configured rule. Preserve the distinction during migration.
Plan your migration with us. Bring a redacted item list, one BOM, a stock count and a partially received purchase order. We will map the pilot with your stores, planning and purchasing owners.
Related Posts

Kanban System | Optiwise
Learn how a Kanban system works in manufacturing, where it helps, where it fails, and how Optiwise connects Kanban signals with inventory, purchase, and production planning.
12 Jun 2026Read more →
ERP for Factory Operations: Follow Each Handoff
Follow a manufacturing order through material planning, buying, production, inspection and dispatch, with an owner for each delay or exception.
12 Jun 2026Read more →
ERP for FMCG Companies in India
A practical guide to ERP for FMCG companies in India, covering distributor orders, batch tracking, expiry, inventory, production, schemes, costing, and reporting.
11 Jun 2026Read more →
Optiwise, Odoo, Acumatica and Business Central for Manufacturing
Compare manufacturing workflows in Optiwise, Odoo, Acumatica and Dynamics 365 Business Central. See what your factory can run in Optiwise.
11 Jun 2026Read more →

