# Job Shop ERP Data Migration Worksheet

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

## Short answer

Plan a data migration object by object: source, record count, data quality, owner and estimated effort hours. A planning sheet for JobBOSS, E2, Global Shop, ProShop or Fulcrum projects.

## Category

erp-migration

## Industry

Job Shop Machining

## Audience

- ERP administrator
- Project manager
- Operations manager

## Tool

**Kind:** worksheet

**Mode:** editable

**Currency:** $

**Columns:**

#### Data object

**Key:** object

**Type:** text

#### Source

**Key:** source

**Type:** select

**Options:**

- Old ERP
- Spreadsheet
- Accounting package
- Paper
- CAD or PLM

#### Record count

**Key:** records

**Type:** number

**Format:** integer

#### Base hours per 1,000 records

**Key:** hrs_1k

**Type:** number

**Format:** decimal

#### Data clean percent

**Key:** clean_pct

**Type:** number

**Format:** percent

#### Estimated effort hours

**Key:** est_hrs

**Type:** number

**Expr:** records / 1000 * hrs_1k * (2 - clean_pct / 100)

**Format:** decimal

#### Owner

**Key:** owner

**Type:** text

#### Status

**Key:** status

**Type:** select

**Options:**

- Not started
- Extracting
- Cleaning
- Loaded to test
- Validated
- Done

**Rows:**

**Object:** Customers and contacts

**Source:** Old ERP

**Records:** 850

**Hrs 1k:** 6

**Clean pct:** 70

**Owner:** Sales admin

**Status:** Cleaning

**Object:** Vendors

**Source:** Old ERP

**Records:** 420

**Hrs 1k:** 6

**Clean pct:** 80

**Owner:** Purchasing

**Status:** Extracting

**Object:** Part master

**Source:** Old ERP

**Records:** 5200

**Hrs 1k:** 8

**Clean pct:** 60

**Owner:** Engineering

**Status:** Cleaning

**Object:** Bills of material

**Source:** Old ERP

**Records:** 1800

**Hrs 1k:** 12

**Clean pct:** 65

**Owner:** Engineering

**Status:** Not started

**Object:** Routings

**Source:** Old ERP

**Records:** 2400

**Hrs 1k:** 10

**Clean pct:** 55

**Owner:** Estimating

**Status:** Not started

**Object:** Open purchase orders

**Source:** Old ERP

**Records:** 140

**Hrs 1k:** 15

**Clean pct:** 90

**Owner:** Purchasing

**Status:** Not started

**Object:** Inventory on hand

**Source:** Spreadsheet

**Records:** 1900

**Hrs 1k:** 10

**Clean pct:** 50

**Owner:** Stockroom

**Status:** Not started

**Object:** Open AR and AP

**Source:** Accounting package

**Records:** 260

**Hrs 1k:** 12

**Clean pct:** 95

**Owner:** Controller

**Status:** Not started

**Totals:**

#### Total records

**Key:** records

**Agg:** sum

**Format:** integer

#### Total effort hours

**Key:** est_hrs

**Agg:** sum

**Format:** decimal

#### Average data cleanliness

**Key:** clean_pct

**Agg:** avg

**Format:** percent

**Summary:**

#### Weeks for one person at 20 hrs per week

**Key:** weeks_one_person

**Expr:** sum_est_hrs / 20

**Format:** weeks

**Primary:** true

#### Labor cost at 70 per hour

**Key:** cost_at_70

**Expr:** sum_est_hrs * 70

**Format:** currency

**Notes:** The effort formula adds up to double the base hours when data is fully dirty (0 percent clean) and the base hours when it is fully clean. Base hours per 1,000 records are planning assumptions: replace them with figures from your own trial loads.

## Content

**Intro:** Data migration is where most small shop ERP projects lose time. This worksheet lists each data object, how many records it has, how clean it is and who owns it, and estimates the effort so the plan is based on something more than a guess.

**Sections:**

#### How to use the migration worksheet

**Body:** List every data object you must carry into the new ERP: customers, vendors, parts, bills of material, routings, work centers, open orders, inventory and open balances. For each, enter the source system, record count, a base hours per 1,000 records assumption and an honest percent clean. The worksheet calculates effort hours, then totals them and converts the total into weeks for one person. Update status as each object moves from extraction through cleaning, test load and validation.

#### How the effort estimate works

**Body:** Effort equals records divided by 1,000, times base hours per 1,000, times a dirtiness factor of two minus the clean fraction. Perfectly clean data costs the base hours. Fully dirty data costs double. The factor is a planning simplification, not a measured law, so calibrate it: load a sample of each object into a test environment, time the cleanup, and replace the assumptions. Complex objects such as bills of material and routings carry higher base hours than customers or vendors.

**Bullets:**

- Parts, BOMs and routings usually dominate effort
- Inventory needs a physical count before load
- Open AR and AP must tie to the general ledger
- Decide what not to convert and archive it instead

#### Sequencing the work

**Body:** Load in dependency order: customers, vendors, work centers and units first, then parts, then bills of material and routings, then open orders and inventory, and finally balances. A part cannot be loaded cleanly if its units of measure or vendors do not exist yet. Plan at least two trial loads before the final one, and reconcile each against source counts and values.

#### Common mistakes

**Body:** Shops overrate how clean their data is, forget to assign owners, migrate years of inactive parts, and discover missing fields during the final load. Take a hard look at the part master first. It is almost always the largest and messiest object.

**Cta:** If you want a second set of eyes on migration scope, or tooling to profile and compare source and target data on your own network, we can help. Data never needs to leave your environment.

**Faq:**

#### How many trial loads should I plan?

**Answer:** Plan at least two full trial loads plus the final cutover load. The first finds structural problems like missing fields and mapping errors, the second proves fixes, and the final should be a rehearsed repeat with no surprises.

#### Should I migrate inactive parts?

**Answer:** Usually not. Migrate parts used in the last two or three years or on open orders, and archive the rest. Fewer, cleaner records make the new system faster and the project cheaper.

#### What does clean percent mean?

**Answer:** It is your estimate of how many records in that object could load without fixes: no duplicates, no missing required fields, correct units. Sample a hundred records and count the ones needing edits to get an honest number.

#### Can this worksheet be used for any ERP?

**Answer:** Yes. The objects and sequencing are generic to job shop and discrete manufacturing ERPs, whether you are moving between JobBOSS, E2, Global Shop Solutions, ProShop, Fulcrum or something else.

## Search terms

erp data migration worksheet, data migration plan template excel, job shop data conversion, erp data cleanup checklist, migration effort estimate, data mapping template erp, erp conversion plan small business, master data migration template

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