# Job Shop ERP CSV Import Template Generator for Parts, Routings and Customers > Source: https://netray.co/tools/job-shop-erp-csv-import-template-generator > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Build clean CSV layouts for parts, routings and customers before loading them into a new job shop ERP. ## Category erp-migration ## Industry Job Shop Manufacturing ## Audience - ERP administrator - Implementation consultant - Shop owner ## Tool **Kind:** template **Output:** code **Language:** text **Fields:** #### Delimiter **Key:** delim **Type:** select **Options:** - , - ; - | **Default:** , #### Sample part number **Key:** part **Type:** text **Default:** BRKT-4410-A #### Sample description **Key:** desc **Type:** text **Default:** Mounting bracket 6061-T6 #### Sample revision **Key:** rev **Type:** text **Default:** C #### Sample material **Key:** material **Type:** text **Default:** 6061-T6 ALUM BAR 1.50 DIA #### Sample customer ID **Key:** cust **Type:** text **Default:** CUST-0192 #### Sample work center **Key:** wc **Type:** text **Default:** VMC-02 **Blocks:** #### Part master file: parts.csv **Body:** part_number{{delim}}revision{{delim}}description{{delim}}uom{{delim}}material_spec{{delim}}std_cost{{delim}}customer_id {{part}}{{delim}}{{rev}}{{delim}}{{desc}}{{delim}}EA{{delim}}{{material}}{{delim}}18.40{{delim}}{{cust}} #### Routing file: routings.csv **Body:** part_number{{delim}}revision{{delim}}op_seq{{delim}}work_center{{delim}}description{{delim}}setup_hours{{delim}}run_hours_each{{delim}}outside_vendor {{part}}{{delim}}{{rev}}{{delim}}10{{delim}}SAW-01{{delim}}Cut to length{{delim}}0.25{{delim}}0.01{{delim}} {{part}}{{delim}}{{rev}}{{delim}}20{{delim}}{{wc}}{{delim}}Mill all features{{delim}}1.50{{delim}}0.12{{delim}} {{part}}{{delim}}{{rev}}{{delim}}30{{delim}}DEBURR{{delim}}Deburr and inspect{{delim}}0.10{{delim}}0.03{{delim}} {{part}}{{delim}}{{rev}}{{delim}}40{{delim}}OUTSIDE{{delim}}Anodize{{delim}}0{{delim}}0{{delim}}VENDOR-ANODIZE #### Customer file: customers.csv **Body:** customer_id{{delim}}name{{delim}}bill_to_address{{delim}}ship_to_address{{delim}}terms{{delim}}tax_exempt {{cust}}{{delim}}Sample Aerospace Inc{{delim}}100 Main St{{delim}}200 Dock Rd{{delim}}Net 30{{delim}}N #### Validation rules to run before loading **Body:** 1. part_number plus revision must be unique in parts.csv. 2. Every part_number and revision in routings.csv must exist in parts.csv. 3. op_seq must be a unique positive integer per part and revision. 4. work_center must match a work center already created in the new system. 5. Hours must be numeric with a period as decimal separator. 6. Rows with an outside_vendor must use a work center flagged as outside. 7. customer_id in parts.csv must exist in customers.csv. 8. No blank part numbers, no leading or trailing spaces, UTF-8 encoding. **Notes:** These are neutral layouts to organize your data, not the import format of any specific product. Every ERP has its own required columns and codes, so map this layout to the vendor's import template. Remove commas from text values, or quote them, if you use a comma delimiter. ## Content **Intro:** Moving to a new job shop ERP almost always means moving parts, routings and customers from spreadsheets or an old system. This generator gives you a clean, consistent layout and the checks to run before any import. **Sections:** #### How to use the templates **Body:** Choose a delimiter, adjust the sample values and copy the three layouts into separate files. Fill them from your legacy system using exports and cleanup in Excel. Then check the data against the validation rules before handing it to your vendor or running an import. Most failed imports come from mismatched keys, not from complicated problems. **Bullets:** - Load customers first, then parts, then routings - Keep part number and revision together as the key - Run a test import into a sandbox before the real one #### What to clean before migrating **Body:** Do not migrate every part you have ever made. Limit parts to those ordered in the last few years, and clean duplicate customers and inconsistent units of measure. Routings built from old estimates often carry guessed hours that should be refreshed from actual times where possible. #### Mapping to a vendor template **Body:** Each vendor names fields differently and may split data across more tables, such as separate estimate, quote and job histories. Map your columns one by one to the vendor's import file and note anything with no match. Those gaps usually decide whether you need a script, a manual load or a decision to leave the data behind. **Cta:** If you need help cleaning and mapping legacy data before an ERP switch, Netray can review your files and flag problems before the load. **Faq:** #### Should I migrate open jobs or start fresh? **Answer:** Many shops migrate open orders and sales history but let in-progress jobs finish in the old system. If you migrate open jobs, plan a single cutover date and reconcile WIP costs at that moment. #### How much history should I move? **Answer:** Most small shops move parts, routings and customers for active items plus a few years of order history for repeat quoting. Older data is often archived read-only instead of imported. #### Why is part revision part of the key? **Answer:** The same part number can have different routings and costs by revision. Using only the part number overwrites data and breaks traceability for aerospace and medical customers. #### Can this template load directly into my ERP? **Answer:** Not directly. It is a neutral layout. Use your vendor's import template for the actual load and use this one to organize and validate the data first. ## Search terms ERP data import template CSV, part master import template, routing import CSV, JobBOSS import template, ERP data migration job shop, customer master import CSV, machine shop data migration --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json