# ERP Data Migration Load Planner Worksheet (IFS, QAD, Plex)

> Source: https://netray.co/tools/ifs-data-migration-load-planner-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

List each data object to migrate with record counts, cleansing progress and an estimated load time to plan trial loads and cutover.

## Category

erp-migration

## Erp

IFS

## Audience

- Data migration lead
- ERP project manager
- ERP consultant

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Data object

**Key:** object

**Type:** text

#### Source system

**Key:** source

**Type:** text

#### Business owner

**Key:** owner

**Type:** text

#### Load wave

**Key:** wave

**Type:** select

**Options:**

- Wave 1 master data
- Wave 2 open transactions
- Wave 3 balances
- Wave 4 history

#### Records

**Key:** records

**Type:** number

**Format:** integer

#### Cleansed (%)

**Key:** clean

**Type:** number

**Unit:** %

#### Load speed (records per minute)

**Key:** rate

**Type:** number

**Format:** integer

#### Load time (minutes)

**Key:** minutes

**Type:** number

**Expr:** records / max(rate, 1)

**Format:** minutes

#### Records to clean

**Key:** uncleaned

**Type:** number

**Expr:** records * (100 - clean) / 100

**Format:** integer

**Rows:**

**Object:** Parts

**Source:** Legacy item table

**Owner:** Engineering

**Wave:** Wave 1 master data

**Records:** 18500

**Clean:** 70

**Rate:** 400

**Object:** Customers

**Source:** Legacy customer table

**Owner:** Sales

**Wave:** Wave 1 master data

**Records:** 2300

**Clean:** 85

**Rate:** 300

**Object:** Suppliers

**Source:** Legacy vendor table

**Owner:** Purchasing

**Wave:** Wave 1 master data

**Records:** 1400

**Clean:** 80

**Rate:** 300

**Object:** Open purchase orders

**Source:** Legacy PO lines

**Owner:** Purchasing

**Wave:** Wave 2 open transactions

**Records:** 3200

**Clean:** 60

**Rate:** 250

**Object:** Stock balances

**Source:** Legacy inventory

**Owner:** Warehouse

**Wave:** Wave 3 balances

**Records:** 42000

**Clean:** 90

**Rate:** 600

**Object:** Open shop orders

**Source:** Legacy work orders

**Owner:** Production

**Wave:** Wave 2 open transactions

**Records:** 850

**Clean:** 75

**Rate:** 200

**Totals:**

#### Total records

**Key:** records

**Agg:** sum

**Format:** integer

#### Total load time

**Key:** minutes

**Agg:** sum

**Format:** minutes

#### Records still to clean

**Key:** uncleaned

**Agg:** sum

**Format:** integer

**Summary:**

#### Total load time in hours

**Key:** load_hours

**Expr:** sum_minutes / 60

**Format:** hours

#### Share of records still to clean

**Key:** clean_share

**Expr:** sum_uncleaned / max(sum_records, 1) * 100

**Format:** percent

**Notes:** Measure load speed in a trial load rather than guessing, since it depends on the load method, validations and environment. Load speed per object usually drops when business rules and custom validations are switched on. Load time here assumes sequential loads; parallel loads change the picture.

## Content

**Intro:** Data migration is the part of an ERP project most likely to overrun. This worksheet lists each object with its owner, cleansing progress and an estimated load time, so you can plan trial loads and the cutover window with numbers.

**Sections:**

#### How to use it

**Body:** Add a row per data object, such as parts, customers, suppliers, bills of material, open orders and stock balances. Enter the number of records from the source system, the percentage already cleansed and a load speed in records per minute from a trial load. The sheet then calculates load time and the number of records still to clean. Assign a wave to each object so that dependencies are respected: master data must load before transactions that refer to it.

#### Choosing waves and sequence

**Body:** Wave 1 is master data, because everything else refers to it. Wave 2 covers open transactions such as purchase and shop orders. Wave 3 loads balances, including stock and the general ledger, which need reconciliation immediately. Wave 4 is history, which is often loaded later or archived instead of migrated. Keep the sequence consistent between trial loads and final cutover, so timings are comparable.

#### Reading the totals

**Body:** Total load time shows whether the cutover fits in your window, for example a weekend. If it does not, consider parallel loads, migrating fewer records, or loading history after go-live. The share of records still to clean shows where cleansing effort should go. A large remaining volume in objects with slow load speeds is a double risk, because late fixes mean a long reload.

#### Common mistakes

**Body:** Estimating load speed from a small sample makes totals look better than reality. Teams also forget reconciliation time, which can match or exceed load time for balances. Another trap is cleaning data in the source after the extract has been taken, so the cleansed version is never the one that gets loaded. Fix data at the source and re-extract.

**Cta:** If you want a second opinion on your load plan or help with reconciliation, we can review it with you.

**Faq:**

#### Is this specific to IFS?

**Answer:** No. The objects and approach apply to any ERP, including QAD and Plex. The IFS name in the title reflects the search audience, and you can rename columns and objects to match your own system.

#### How do I get load speed?

**Answer:** Run a trial load of a representative sample with business rules and validations switched on, then divide records loaded by elapsed minutes. Repeat on a full-size trial to confirm.

#### Should history be migrated?

**Answer:** Often only a limited period is migrated, and older history is archived in a read-only store. Decide based on reporting, warranty and legal retention needs, not on convenience.

#### How much cleansing is enough?

**Answer:** Aim for full cleansing of anything that will be used from day one, such as active parts, customers and open orders. Inactive records can be excluded rather than cleaned.

## Search terms

erp data migration plan template, ifs data migration worksheet, data load planner excel, erp cutover load time estimate, master data migration checklist excel, data migration tracker

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json