An EDGEBIC Migration Checklist

An EDGEBIC migration checklist runs in six phases: prepare and clean data, build masks, import in dependency order, verify capacity, run a pilot, and expand. In EDGEBIC by User Solutions, every step is low risk because RMDB stays the system of record and imports come through saved masks. The checklist is a sequence of small, reversible steps, not a single cutover, so a small team can work it part time and finish when EDGEBIC has earned the schedule rather than when a deadline arrives.

How to use this checklist

Work the phases in order, but treat them as a loop, not a one-way march. Because import masks are saved and RMDB stays supported, you can go back a phase, fix something, and re-run in a click without penalty. The point of the checklist is that nothing surprises you: each phase has a clear job, and each job is small. The whole thing fits the phased approach on the RMDB to EDGEBIC guide.

The six phases at a glance

Phase 1: prepare

• Choose the pilot cell. Pick a self-contained work area with a clear bottleneck, stable routings, and an engaged planner. Details are in planning an EDGEBIC pilot on one cell.
• Clean the scheduled tree. Standardize product and work center names across all files, fill required fields (setup and run times, quantities, due dates), and drop dead references. Clean only what scheduling reads, covered in cleaning your data before importing to EDGEBIC.

Phase 2: build masks

• Export each entity. Send products, work centers, customers, routings, and open orders out of RMDB in their existing layouts.
• Map columns once. Build one import mask per entity, mapping your columns to EDGEBIC's fields, and save each mask. The mechanics are in EDGEBIC import masks explained.
• Confirm blank-cell handling. Check how each mask treats empty cells so a blank does not clear a value you meant to keep.

Phase 3: import in dependency order

• Products and work centers first. These are the foundation everything references.
• Then customers, then routings, then orders. References link by name, so the target must exist before the pointer. The full reasoning is in the order to import your data into EDGEBIC.
• Let the two-pass routing import handle sequence. It wires step order inside the routing file for you.

Phase 4: verify capacity and calendars

• Set shifts, holidays, and calendars. Bring across your shift patterns and plant holidays, either through their import masks or by keying them in, then attach the calendars and add any per-day capacity overrides.
• Reconcile capacity before reading a date. Confirm EDGEBIC's capacity per work center matches your current system, work center by work center. This is the step that keeps every later date comparison honest, and it is the guard against wrong-but-plausible dates.

Phase 5: run the pilot

• Schedule the cell. Run a scheduling pass on the pilot cell.
• Compare dates. Line up EDGEBIC's dates against your existing plan for the same jobs, and reconcile every difference at the source. The validation discipline is in validating a migrated schedule against RMDB.
• Keep RMDB in charge. The plant runs on RMDB; the cell is a controlled comparison, the pattern in running RMDB and EDGEBIC side by side.

Phase 6: expand and cut over

• Widen cell by cell. Add a cell only when the planners stop double-checking the last one's dates.
• Handle open jobs at cutover. Let short jobs finish on RMDB and import new work clean, per migrating open jobs and actuals to EDGEBIC.
• Complete the cutover on your timeline. RMDB stays supported, so you finish when EDGEBIC has earned the schedule, covered in completing the cutover to EDGEBIC.

Where the effort actually is

The checklist looks long, but the effort is not evenly spread. Phases 2 and 3, building masks and importing, are the real work, and they are a few days done once. After that, every import is a one-click re-run of a saved mask. Phase 5, the pilot loop, is a planner spending a few minutes each cycle on a comparison. Nothing on the list is a standing full-time commitment, which is why a small team can work it part time.

The one item not to skip, however busy you are, is the capacity verification in phase 4. It is quick, and it is what makes every later comparison meaningful. Skip it and you will chase date differences that were only ever a missing holiday.

Why the checklist is low risk

Every phase is reversible. Cleaning happens in the spreadsheet, before anything is imported. Imports re-run in a click because the masks are saved. The pilot keeps RMDB as the system of record, so the plant is never at stake. And there is no forced cutover, because RMDB stays fully supported for as long as you want it. The result is a migration made of small, reversible steps, which is exactly how a cautious shop should take on a new tool.

The takeaway

An EDGEBIC migration checklist is six phases: prepare and clean, build masks, import in dependency order, verify capacity, run a pilot, and expand. The heavy work is front-loaded into mask building and cleaning, a few days done once, and everything after is a one-click re-run or a few minutes of comparison per cycle. Verify capacity before you read a date, keep RMDB in charge until EDGEBIC earns the schedule, and move at your own pace because there is no forced cutover. See the platform in full on the EDGEBIC overview, read the whole path on the RMDB to EDGEBIC guide, and turn the list into a timeline with a phased migration plan to EDGEBIC. For the whole subject end to end, read the complete guide to migrating to EDGEBIC.