Week 5 of 8

Data imports and migration

Most ERP data arrives through an import tool: Epicor’s DMT, Acumatica import scenarios, Sage Intacct CSV templates, Odoo’s import screen, IFS Data Migration Manager. These tools run your data through the system’s business logic. That is good for data quality, and it means an import can break when the logic or the template changes.

Sage Intacct says it plainly: its import templates are updated periodically, especially with a new release, and an older template might not work. Treat every template as a test object, before go-live and after every release.

This week: build an import validation routine

List every import you run: master data, opening balances, open items, recurring loads from other systems. Note the tool and template version.
Use the tool’s own validation first: Odoo’s Test button, DMT’s required-field checks, a small trial file of a few rows.
Reconcile every load: record counts, control totals and a sample of field-level checks, with tolerances agreed with finance before the first mock.
Re-download or re-validate templates after every vendor release, and keep the last good file for comparison.

Number of the week

60+

pre-designed import templates ship with Epicor’s Data Migration Tool, which validates data against business logic and flags required fields.

Source: Epicor, Data Migration Tool product page

Use this week

ERP Data Import Validation Tracker →
Every import object with template version, pre-checks, counts, control totals and a pass/fail per load and per release.
Mock Cutover Rehearsal Tracker →
Goals and timings for each rehearsal, so the loads fit the cutover window.

Next week: roles. The test user with every permission is the most expensive shortcut in ERP testing.

Get the playbook in your inbox, one week at a time

Subscribe free and every template in the library is yours.