An ERP implementation Iraq project succeeds only when the new system starts with trusted data. Migration should clean and map master records, transfer approved opening balances and open transactions, rehearse the cutover, and prove that finance, inventory, customers, suppliers, and branches reconcile before go-live.
Quick answer: Do not move every spreadsheet into the ERP. Decide what must operate on day one, assign an owner to each data set, remove duplicates, map fields, run at least two full migration rehearsals, reconcile totals to the legacy system, freeze changes during cutover, and obtain business sign-off before users post new transactions.
Disclaimer: This guide is for general information only and is not legal, tax, accounting, cybersecurity, or compliance advice. Retention requirements, accounting treatments, privacy obligations, and system controls vary. Verify decisions with qualified advisors and relevant Iraqi authorities before deleting, transforming, or relying on business records.
Hanooot is an Iraqi operating partner founded in Baghdad in 2022. We implement software for Iraqi finance, inventory, purchasing, sales, branches, Arabic workflows, and IQD reporting. The ERP and software service in Iraq connects process design, migration, integrations, training, and launch.
What is ERP data migration?
ERP data migration is the controlled movement of business records from spreadsheets, accounting packages, POS tools, warehouse files, or an old ERP. It includes extraction, cleansing, mapping, loading, validation, reconciliation, approval, and archiving.
Success means users can operate and explain every opening figure, not merely that a file imported without error.
1. Master data defines the business
Items, customers, suppliers, branches, warehouses, accounts, users, and approval roles tell the ERP how to operate.
2. Opening positions define day one
Cash, receivables, payables, inventory, assets, and ledger balances determine whether the first report is credible.
3. Open transactions keep operations moving
Open orders, unpaid invoices, deposits, advances, and goods in transit need a clear day-one treatment.
Which data should move into the new ERP?
Move data because the business needs it. Day-one operations usually need clean masters, balances, open items, active orders, current stock, and a controlled archive.
| Data set | Typical day-one choice | Control question |
|---|---|---|
| Chart of accounts | Migrate active, approved accounts | Does every account have a clear purpose and owner? |
| Customers and suppliers | Active records plus required balances | Have duplicates and spelling variants been merged? |
| Items and units | Active SKUs, barcodes, units, costs | Do branch and warehouse codes mean the same thing? |
| Inventory | Quantity, location, batch where needed, value | Does physical stock reconcile to the opening file? |
| Receivables and payables | Open invoices, credits, advances | Can each balance be collected, paid, or explained? |
| Historical transactions | Selective detail or controlled archive | Is detail needed for service, audit, tax, or analysis? |
| Users and roles | Active staff with least necessary access | Has management approved permissions? |
Figures and choices are indicative and can change by business scope, authority review, exchange rate, and current regulation. Verify before making a financial decision.
Who owns each migration data set?
Technology moves data; the business approves its meaning. Assign a named owner and acceptance rule before extraction.
1. Finance owns accounting truth
Finance approves accounts, opening balances, bank positions, assets, tax fields, and reconciliation rules.
2. Operations owns item and workflow truth
Operations approves items, units, warehouses, purchasing states, order statuses, and branch practices.
3. Sales and procurement own commercial masters
These teams confirm customer, supplier, price, payment-term, credit-limit, and active-order data.
4. IT owns the controlled migration process
IT manages extracts, mapping, scripts, access, logs, sequence, environments, backups, and repeatability. The business signs off on the result.
How should the data be cleaned and mapped?
Profile rows, blanks, duplicates, invalid dates, unexpected currencies, inactive records, negative quantities, and inconsistent codes. Check hidden spaces, mixed dates, and duplicated IDs.
Build a controlled data dictionary with the old field, new field, rule, owner, accepted values, and test result. Standardize IQD codes, customer identifiers, and warehouse aliases.
For importers, connect items to units, suppliers, currencies, landed-cost categories, and destinations. Do not copy unverified regulatory classifications from old spreadsheets.
What migration sequence reduces risk?
Load data in dependency order. A customer invoice cannot load cleanly before its customer, currency, account, and branch exist.
- Configuration and reference values: currencies, fiscal periods, units, branches, warehouses, tax or accounting settings.
- Core masters: chart of accounts, items, customers, suppliers, employees, assets, and users.
- Opening quantities and balances: stock, ledger, bank, receivables, payables, advances, and assets.
- Open operational transactions: purchase orders, sales orders, goods in transit, pending returns, and commitments.
- Selected history: only after day-one operations reconcile and performance has been tested.
Microsoft's Dynamics 365 go-live guidance recommends repeated tests, data validation, cutover performance checks, issue logging, and business sign-off. These principles apply across ERP brands.
How many rehearsal migrations should you run?
Run the full process, not just sample imports. A focused SME rollout should plan at least two complete rehearsals. Complex multi-branch or integrated environments may need three or more.
| Run | Main purpose | Minimum exit condition |
|---|---|---|
| Rehearsal 1 | Expose field, quality, and sequence problems | Every rejected row has a reason and owner |
| Rehearsal 2 | Prove corrected rules and reconciliation | Key totals agree and timing fits the window |
| Rehearsal 3 when needed | Simulate production volumes and users | Cutover steps, roles, rollback, and sign-off pass |
| Production cutover | Create the approved day-one position | Business owners approve before posting starts |
Figures and choices are indicative and can change by business scope, authority review, exchange rate, and current regulation. Verify before making a financial decision.
Each rehearsal should use a versioned extract, intended scripts, planned load order, reconciliation reports, and a timed runbook. Manual test fixes warn that production may not be repeatable.
How do you reconcile finance, inventory, and open items?
Reconciliation proves the migration. Compare control totals before and after loading, then investigate differences to the transaction level.
Microsoft's finance reconciliation guidance recommends matching open balances, subledgers, and the ledger, then completing a mock close before go-live.
1. General ledger
The opening trial balance should match by account, branch, and currency, with debit equal to credit.
2. Accounts receivable and payable
Customer items should total to receivables and supplier items to payables. Advances, credits, and disputes need explicit treatment.
3. Inventory
Reconcile quantity by item and location, then value by the approved costing basis. Approve count differences before migration.
4. Bank and cash
Tie openings to bank statements and signed cash counts. Define treatment for outstanding payments and deposits.
Worked example: reconciling an opening migration
Assume a Baghdad wholesaler plans to migrate 3,800 active SKUs, 620 customers, and 145 suppliers. Its first rehearsal produces these totals:
- Legacy inventory value: IQD 1,240,000,000
- ERP inventory after load: IQD 1,228,600,000
- Initial difference: IQD 1,240,000,000 − IQD 1,228,600,000 = IQD 11,400,000
The team investigates:
- 18 SKUs with missing unit conversion: IQD 7,200,000
- 6 duplicated negative adjustments excluded by mistake: IQD 3,100,000
- Rounding across foreign-currency costs: IQD 1,100,000
- Explained total: 7,200,000 + 3,100,000 + 1,100,000 = IQD 11,400,000
After correction and rerun, ERP inventory equals IQD 1,240,000,000. The team still samples high-value items and branches because matching totals can conceal offsetting errors.
What should happen during cutover weekend?
Cutover is the controlled move from old tools to the new ERP. Define the freeze, owner, sequence, deadline, decision authority, rollback condition, communication, and support plan.
1. Freeze and capture
Stop or tightly control new transactions in the legacy tools. Record the final invoice, receipt, payment, stock movement, and timestamp included in the extract.
2. Load and validate
Run approved scripts. Count accepted and rejected records. Reconcile totals. Do not let users begin posting while finance and inventory positions remain unexplained.
3. Approve or roll back
Named approvers should use measurable criteria: zero unexplained ledger difference, approved inventory variance, passed critical integrations, and confirmed access.
4. Monitor the first operating cycle
Reconcile sales, purchases, stock, cash, and bank interfaces daily in week one. Complete an early month-end close to expose structural errors.
For a broader rollout plan, read Hanooot's ERP implementation guide and guide to moving beyond spreadsheets.
What migration mistakes should Iraqi businesses avoid?
- Migrating every historical row without a use case. This increases time, storage, privacy, and reconciliation risk.
- Letting IT approve financial meaning. Technology teams can map fields; finance must approve balances and accounting treatment.
- Changing source files after sign-off. Version every extract and transformation rule.
- Ignoring Arabic and English duplicates. One customer or supplier may appear under several spellings; use controlled identifiers and approved display names.
- Skipping production-volume testing. A script that loads 1,000 rows quickly may miss the cutover window with millions.
- Keeping spreadsheets as a parallel system. Define when the ERP becomes the source of truth and which archives remain read-only.
Hanooot support for ERP data migration
Hanooot maps workflows, cleans data, defines ownership, configures ERP, builds repeatable routines, runs rehearsals, trains users, and supports cutover and reconciliation.
The scope should follow the operating model: retailers need trusted branch stock; distributors need purchase, landed-cost, and receivable controls; service companies need explainable customer, project, payroll, and accounting records.
Frequently asked questions
What data should an Iraqi business migrate into a new ERP?
Most businesses migrate approved master data, opening balances, open customer and supplier items, current inventory, active orders, and only the history needed for operations or reporting. Old detail can remain in a controlled archive when moving it would add risk without business value.
How many ERP migration test runs are needed?
Plan at least two complete rehearsals for a focused project and more when data, branches, integrations, or transaction volumes are complex. Each rehearsal should use the same extraction, transformation, loading, reconciliation, sign-off, and timing controls planned for go-live.
How do you prove ERP opening balances are correct?
Reconcile the legacy trial balance to the ERP ledger, customers to accounts receivable, suppliers to accounts payable, inventory quantities and value to stock records, and cash to bank evidence. Differences should have named owners and approved explanations before transactions begin.
Can Hanooot manage ERP data migration in Iraq?
Yes. Hanooot maps Iraqi business processes, cleans and transforms data, configures ERP controls, runs migration rehearsals, supports user acceptance, and coordinates cutover and post-launch reconciliation for growing businesses.
Conclusion: migrate evidence, not uncertainty
ERP migration is a control project: select day-one data, approve its meaning, rehearse the process, reconcile totals, and open only when the new position is explainable.
For ERP implementation in Iraq, Hanooot can assess source data, design migration, run rehearsals, and support launch. Start through the contact page to plan around finance, inventory, and branch operations.