Migration planning
Plan the migration before you commit to it
Most migration trouble is decided before the project starts, by what was and was not known when the scope, budget and date were set. Planning turns an uncertain estate into an inventory, a list of risks with owners and a sequence that respects partner and business calendars. It is also the point at which replacing, upgrading or staying put can still be compared on facts.
At a glance
- Inventory workshop and data collection
- Partner segmentation
- Risk register
- Target and delivery model comparison
- Migration plan
- Estimating from facts
What is EDI migration risk assessment?
An EDI migration risk assessment identifies what could go wrong when moving EDI from one platform or provider to another, rates each risk by likelihood and effect on the business, and assigns a mitigation and an owner. It covers technical risks, such as map differences and acknowledgment handling, and business risks, such as partner scorecards, peak periods and dependence on a single specialist.
Outcomes
What you can expect
Decisions based on an inventory
A shared list of partners, documents, connections and interfaces replaces estimates and memory, and exposes dormant items that need not be migrated.
Risks named while they are cheap to address
Risks identified in planning can be mitigated by design. The same risks found during cutover are handled under pressure.
Sequence that fits the business
Waves are set around partner calendars, freezes and contract dates instead of project convenience.
A clear go or no-go
Defined criteria for each wave, and for rollback, replace gut feeling on the night of cutover.
Approach
How ECOM delivers it
-
Inventory workshop and data collection
Collect partners, document types, maps, schedules, communication methods, certificates and ERP interfaces, with owners and last-used information.
-
Partner segmentation
Group partners by complexity, volume, penalties for lateness and testing effort, which sets the order of the waves.
-
Risk register
Record each risk with a likelihood, a business effect, a mitigation and an owner, and review it through the project.
-
Target and delivery model comparison
Compare keeping, upgrading, modernizing and replacing, and hosted, managed or self-run delivery, against the inventory and constraints.
-
Migration plan
Define waves, test approach, cutover windows, communication, rollback criteria and hypercare, and show dependencies between them.
-
Estimating from facts
Estimate effort and duration from the inventory rather than a standard figure, and state the assumptions and the unknowns.
What the register covers
Risk areas that deserve a line in every plan
-
Undocumented map logic
Rules embedded in maps and scripts that nobody remembers. Mitigated by map analysis and parallel comparison.
-
Partner requirement drift
Partner specifications that changed since the original setup. Mitigated by reconfirming requirements before building.
-
Acknowledgment and control number handling
Mismatches that cause rejection or silent loss. Mitigated by validation in test and close observation after cutover.
-
ERP interface changes
Layout, timing or master data differences. Mitigated by testing against the ERP test environment with representative data.
-
Key-person dependency
One or two people holding the knowledge. Mitigated by capture early and a named backup.
-
Calendar collisions
Peak seasons, financial close or partner freezes overlapping a wave. Mitigated by scheduling around them and agreeing freezes.
What you receive
What a planning engagement produces
-
Inventory and dependency map
A documented list of what exists, what is active and how the pieces connect.
-
Risk register and mitigation plan
The risks, their owners and the actions agreed to reduce them.
-
Wave plan and cutover approach
A sequence for partners and interfaces, with test, cutover, rollback and hypercare steps for each wave.
-
Options comparison
A neutral view of keep, upgrade, modernize or replace against your constraints, including the cost of waiting.
-
More time for partner testing
Partners test on their own schedules. Early notice leaves room for retests and delays without jeopardizing a fixed date.
-
More choices at contract dates
Decisions made well ahead of a renewal or support end date allow overlap and negotiation, rather than a rushed extension.
-
Less pressure on the one person who knows the system
Capturing knowledge while that person is still engaged is far easier than reconstructing it afterward.
Scenarios
Common scenarios
Before budgeting a migration
Establish scope and risks well enough to budget and choose between options with some confidence.
Before signing a new platform or provider contract
Check what the migration will actually require before committing to dates and fees.
Recovering a stalled migration
Reassess an in-flight project whose scope or risks were not understood at the start.
Frequently asked questions
Is migration planning separate from the EDI environment assessment?
They are related. The assessment is a structured review of your EDI environment. Planning uses that, or your own inventory, to build the risk register, wave plan and options comparison. Either can come first.
Do we have to commit to ECOM to get a plan?
No. A plan can be used with any provider. Scope, effort and commercial terms for any planning work are agreed with ECOM in advance rather than assumed.
What do you need to begin?
A list of partners and documents, a description of the platform and its connections, ERP details and the dates that constrain you. Incomplete information is normal and is filled in during the work.
How are risks rated?
Each risk gets a likelihood and a business effect, an owner and a mitigation. The scale is agreed with you so the register matches how your business thinks about risk.
Can planning change the decision to migrate?
Yes. Sometimes the right outcome is to upgrade, modernize in place or delay. A plan based on facts should be able to say that.
Plan before you commit
Tell us what you are considering and what dates apply. An ECOM specialist will explain how planning would work for your estate.