# JobBOSS to E2 Shop System Migration Checklist > Source: https://netray.co/tools/jobboss-to-e2-migration-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A practical checklist for moving a small shop from JobBOSS to E2 Shop System, from data audit through cutover and first month close. Works in reverse too. ## Category erp-migration ## Erp JobBOSS ## Industry Job Shop Machining ## Audience - Shop owner - Operations manager - ERP administrator ## Tool **Kind:** checklist **Scoring Note:** Tick items as you finish them. Every critical item must be done before you turn off the old system for data entry. **Groups:** #### 1. Decide and scope **Items:** **Text:** Document why you are leaving JobBOSS (support, cost, reporting, features) and what success looks like **Critical:** true Confirm the license, module and user count you need in E2 and get the quote in writing **Text:** Name one internal project owner with time set aside each week **Critical:** true Check the current JobBOSS version, database type and whether you have an active support plan Agree the cutover window with the shop calendar, avoiding quarter end and peak shipping weeks List integrations to keep: accounting, EDI, CAD, shop floor data collection, shipping #### 2. Clean and extract data **Items:** **Text:** Export customers, contacts and ship-to addresses and remove duplicates and dead accounts **Critical:** true Export vendors with terms, tax status and approved supplier flags **Text:** Export the item or part master with units of measure, revision and costing method **Critical:** true Export bills of material and routings, and spot check twenty active parts against the floor Export work centers, labor rates and overhead rates Archive closed jobs older than your retention need instead of converting them **Text:** Back up the full JobBOSS database before any export and store a copy offline **Critical:** true #### 3. Open transactions **Items:** **Text:** Freeze new job entry for a short, announced window and reconcile open jobs **Critical:** true Decide which open jobs are re-entered with remaining operations only Capture hours and material already posted to each open job so costing stays whole **Text:** Convert open purchase orders with received and remaining quantities **Critical:** true Convert open sales orders and quotes with promise dates Record inventory on hand by location, lot and heat or serial where traced **Text:** Document open AR and AP balances and tie them to the general ledger **Critical:** true #### 4. Test and train **Items:** **Text:** Run a trial load into an E2 test database and compare record counts to the source **Critical:** true Quote, order, schedule, issue, receive, ship and invoice one test job end to end Verify the traveler, packing slip, invoice and certificate formats match what customers expect Check that job costing and WIP numbers on converted jobs match JobBOSS Train office users by role with their own data, not generic demo data Train supervisors and operators on shop floor data entry on the real terminals #### 5. Cutover and stabilize **Items:** **Text:** Run a final data load after the last day of JobBOSS entry and freeze JobBOSS to read only **Critical:** true **Text:** Verify inventory valuation, open AR, open AP and open PO totals on day one **Critical:** true Hold a daily 15 minute issue meeting for the first two weeks Keep JobBOSS available read only for at least one full year for history and audits Complete the first month end close in E2 and compare it to the prior month method Capture lessons learned and update written procedures ## Content **Intro:** Moving a small machine shop from JobBOSS to E2 Shop System is mostly a data and discipline project, not a software install. This checklist walks through scoping, cleaning data, open transactions, testing and cutover in the order shops usually need them. **Sections:** #### How to use this checklist **Body:** Treat each group as a phase gate. Do not start group three until the clean extract in group two has been reviewed by someone who knows the parts and customers. Critical items are the ones that, if skipped, usually cause a bad first month: no backup, unreconciled AR or AP, unverified open purchase orders, or a cutover with no read-only fallback. Export the list to Excel and assign an owner and a date to each line. #### What actually moves and what should not **Body:** Master data moves: customers, vendors, parts, bills of material, routings, work centers and rates. Open transactions move selectively: open jobs, purchase orders, sales orders, inventory and open balances. Closed history usually should not. Converting years of closed jobs adds cost and noise, and you can keep the old database read only for reference. The same logic applies if you are going the other direction from E2 to JobBOSS, since both are job shop systems with similar structures. #### Validation and reconciliation **Body:** Do not accept a load because it finished without errors. Compare record counts per table, inventory value against the general ledger, and open PO and AR totals against the old system. Pick twenty parts and walk each from quote through routing. Check that converted open jobs show hours and material already spent, otherwise job costing will look wrong for months. **Bullets:** - Record counts per object, source versus target - Inventory quantity and value by location - Open AR and AP aging totals - Sample parts with full BOM and routing walk-through #### Common mistakes **Body:** Shops underestimate cleanup, try to convert everything, skip training on the shop floor terminals, and cut over in the busiest week of the quarter. Another frequent miss is forgetting custom reports and forms: the traveler, packing slip and certificate that customers rely on. Rebuild and test those before go live, not after. **Cta:** If you want help extracting and validating data between systems, or loading history into a private searchable archive, we can discuss options. Many shops do the core move themselves with their vendor. **Faq:** #### How long does a JobBOSS to E2 migration take? **Answer:** For a small shop with clean data, expect roughly two to four months from decision to cutover, mostly driven by data cleanup, testing and training. Shops with messy part masters or heavy customization take longer. Treat any vendor timeline as a plan, not a promise. #### Should I convert closed job history? **Answer:** Usually not. Convert master data and open transactions, and keep the old JobBOSS database read only for history, quoting reference and audits. Converting closed jobs adds cost and risk without helping daily operations. #### Can I run both systems in parallel? **Answer:** Short parallel testing on a few jobs is useful, but running both for live production doubles data entry and causes inventory drift. Pick a clean cutover date, freeze the old system, and keep it read only afterward. #### Does this checklist work for other ERP switches? **Answer:** Yes. The phases of scope, clean, open transactions, test and cutover apply to any job shop ERP change, including Global Shop Solutions, ProShop and Fulcrum. Adjust the item names to match your source and target systems. ## Search terms jobboss to e2 migration, switch from jobboss to e2 shop system, e2 shop system migration checklist, jobboss data conversion, job shop erp migration checklist, migrate job shop software, jobboss alternative e2, erp cutover checklist small shop --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json