A move away from an expensive EDI value added network (VAN), a service that routes business documents between trading partners, should not depend on an informal promise to handle the migration. A missed purchase order, duplicate invoice or unresolved acknowledgment can create work long after a connection appears to be live. Put the support responsibilities in writing before you change routes.
Quick Answer
EDI migration support needs a written scope of work that names the partners and documents being moved, assigns owners, defines tests and sets evidence based cutover criteria. With Nexus VAN, dual-VAN reconciliation runs the old and new VANs side by side so documents can be accounted for before the old route is retired. That makes switching low risk and gives you a clear basis for comparing migration costs.
In This Article
- Define the work before switching routes
- Inventory partners, documents and dependencies
- Assign ownership and change control
- Test business outcomes, not just connections
- Reconcile both VANs before cutover
- Put costs and contract exposure in scope
- Apply practical scope of work best practices
- Frequently asked questions
A written scope makes migration risk and cost visible
An EDI migration scope of work is an agreed record of what will change, who will do the work and what must be demonstrated before the project is complete. It is useful to both sides of the table. Finance can see what services are included and what might produce an extra charge. IT can see which connections and application handoffs will change. The EDI coordinator can see who is contacting each partner and what counts as a passed test.
The scope should answer a short set of operational questions: Which trading partners are included? Which documents flow in each direction? Are you changing the network route only, or also changing the way documents are translated for internal systems? Who supplies connection details and test files? What happens if a partner cannot complete testing? Who has authority to approve the production switch?
Do not use a phrase such as "migrate all EDI" as the only description of the work. If a partner has an old route that is rarely used, a second document format or a separate receiving business unit, people can reasonably disagree about whether it was included. Attach an inventory that can be checked line by line. Record exclusions as clearly as inclusions so a later request for an unrelated system change does not silently alter the migration plan.
The practical test: If your EDI coordinator left the project tomorrow, could another person identify every route being moved, the owner of every open task and the evidence required to retire each old route? If not, the scope is not yet specific enough.
An inventory prevents overlooked partners and documents
Start with a partner and document inventory rather than a schedule. An EDI identifier is the code used to identify a sender or receiver, while a qualifier identifies the kind of code in use. Capture the identifiers and qualifiers currently used, then check how each partner expects to address documents after the move. You should also record connection details, any certificates required for secure exchange and the internal application that consumes or produces each document.
For each partner, list document types in both directions. An ANSI X12 850 is a purchase order, an 856 is an advance ship notice and an 810 is an invoice. These transaction numbers identify broad document types; a partner's published EDI implementation guide sets its specific requirements. Check the guide and applicable version instead of assuming that one retailer's 850 tests cover another retailer's 850.
| Record in the scope | What to specify | Why it affects the move |
|---|---|---|
| Trading partner and identifiers | Partner name, sending and receiving IDs and qualifiers | Incorrect addressing can send a document to the wrong route or leave it undelivered. |
| Documents and direction | Transaction type, inbound or outbound flow and applicable version | Each business flow needs its own test and acceptance evidence. |
| Connection method | VAN interconnect, AS2, SFTP or REST API as applicable | Configuration and partner coordination differ by connection method. |
| Internal handoff | Application that sends or receives the document and the owner of that handoff | Network delivery alone does not prove the business system processed the document. |
| Partner requirements | Guide version, required tests, acknowledgment expectations and approval contact | Partner dependent rules can change the testing and cutover plan. |
| Legacy dependency | Old mailbox, route, archive access or contract condition that must remain available | A route may need to stay in place while outstanding documents are reconciled. |
Separate a transport change from a mapping change. A map is the set of rules that converts a document into the form an internal system needs. If the scope says only that messages will move to a new VAN, an ERP interface change should not be assumed. Conversely, if the internal handoff must change, state who will design it, test it and approve it. This distinction prevents a connection test from being mistaken for a complete business test.
For a large partner list, group work into migration waves. A wave is a defined set of partner routes moved and approved together. The scope should say how partners enter a wave, which dependencies must be ready first and what happens to a partner that cannot complete its tests. See our trading partner migration wave plan for a closer look at that sequencing.
Named owners prevent delays and disputed responsibilities
"Customer to provide information" is an assignment to no one in particular. Name a role or person for each deliverable and specify what that person must supply. Some tasks need more than one participant. A provider may prepare a route while the customer obtains approval from a trading partner, and the partner may need to confirm that its side is ready. List all three dependencies rather than declaring the whole task complete when one party finishes.
| Activity | Owner to name in your scope | Evidence of completion |
|---|---|---|
| Approve partner inventory | Customer EDI lead | Reviewed list of active routes, documents and identifiers |
| Confirm internal system handoff | Customer application owner | Agreed description of where each document enters or leaves the application |
| Prepare new connection details | Provider implementation contact and customer IT contact | Configuration ready for the agreed tests |
| Coordinate partner testing | Named partner contact and customer EDI lead | Partner requirements and test results recorded |
| Resolve exceptions | Assigned technical owner and business owner | Cause, corrective action and retest outcome |
| Approve cutover | Named business and technical approvers | Written decision against the agreed acceptance criteria |
Add a simple change process. If a new partner, document type or mapping request appears during migration, who reviews the effect on testing and commercial terms? Who approves the change before work begins? A change record is particularly useful when multiple divisions or portfolio companies are involved. Otherwise, a scope prepared for one entity can gradually become an undefined project for several.
Support coverage also belongs in writing. Name the contacts for a failed test, a business document that is rejected and a partner that changes its requirements. Specify who communicates the issue, who decides whether the wave can continue and who records the resolution. This is more actionable than a general promise of "migration support."
Acceptance tests must prove the business flow works
A successful transmission proves that data reached a connection point. It does not prove that the correct partner received the intended document, that its syntax was accepted or that the receiving business system acted on it. Write a test matrix for each included document and direction. Give each test a sample input, an expected outcome, an owner and a place to record the actual outcome.
- Test transport. Confirm the agreed connection method carries the document to the intended destination. Nexus VAN supports AS2, SFTP and REST API and has interconnects to VANs globally, so the scope should identify the specific route used for each partner rather than assuming all partners connect in the same way.
- Test syntax and partner requirements. Check the transaction against the applicable standard and the partner's published implementation guide. Where the partner requires formal certification, include that activity and the partner's approval in the acceptance record.
- Test acknowledgments. An X12 997 functional acknowledgment tells the sender whether the document passed the receiver's syntax check. It can report acceptance or rejection. It does not mean the order or its business content was accepted. State what other evidence is needed to confirm the business outcome.
- Test internal processing. Have the application owner confirm that an inbound document reaches the intended process and that an outbound document reflects the intended business event. The details depend on your own system and each partner's rules.
- Test exceptions. Include a rejected document, a missing acknowledgment and a suspected duplicate in the handling plan. Record who investigates, how the document is matched and what approval is needed before it is sent again.
A test result should be traceable to a document, not merely marked "passed" in a meeting note. Record its identifier or control number, the relevant acknowledgment, the receiving application result and the person who approved it. Control numbers are identifiers within EDI messages that help the team match what was sent with what was received. For a deeper set of acceptance checks, see our guide to EDI testing and certification acceptance criteria.
Dual-VAN reconciliation supports a low-risk cutover
The hardest migration question is what happened to documents while routes were changing. A purchase order may have been sent just before a partner changed its address. An acknowledgment may return after the new route goes live. If a team resends an uncertain document without checking its status, it may create a duplicate. Write rules for these in-flight documents before moving a production route.
During migration, Nexus VAN runs your old VAN and the new VAN side by side for dual-VAN reconciliation. That means the team can compare what the old route and the new route show, account for each document and resolve exceptions before retiring the old route. Nexus VAN's management portal provides visibility into transaction status, acknowledgments and control numbers. The scope should specify which records your team will review and who will sign off on the comparison.
Side by side operation requires a clear sending rule. Do not assume that every document should be delivered twice. Specify which route is authoritative for each partner and document direction, which records are compared and who can authorize a resend. A comparison that finds a mismatch is useful because it creates an investigation task before the legacy path is removed. It should not be quietly cleared to keep a schedule on track.
Cutover gate: For each route, require the agreed test results, partner readiness where applicable, matched document records and written business and technical approval. If an item is unresolved, keep the route in its agreed prior state while the owner investigates it.
Include a fallback decision in the scope. Identify who can pause a wave, when an old route must remain available and how the team will check for documents already in transit before switching back. A fallback is not a promise that every issue can be reversed instantly. It is a decision path that limits confusion when a test fails or a production document does not reconcile. Our dual-VAN reconciliation guide explains the document matching questions in more detail.
The scope should cover the bill and the exit contract
A migration can be operationally sound and still leave you paying for the old arrangement longer than expected. Before approving the work, review your existing VAN's notice requirements, renewal terms, archive access and any fees tied to keeping old routes available. If an archive export is needed, put its owner and cost in the scope. Do not assume old transaction history moves automatically with live traffic.
Many legacy VANs use charges that can inflate a bill, including rounding each document up in size, minimum charges per document, per-partner fees and archive-access fees. The written scope helps finance distinguish those existing charges from the actual work required for migration. It also gives you a consistent set of documents and partners when comparing a new billing model with your current invoice.
Nexus VAN prices by the kilo-character, and we never round up the size of your documents, so you are billed accurately for the exact data you transmit, and nothing more. When you compare costs, use actual document sizes and identify the separate fees on your current bill. This is more useful than comparing a quoted rate without accounting for rounding or additional charges.
The Spanx case study illustrates why the contract review matters: Spanx left a legacy VAN arrangement with hidden fees, high per-message rates, per-partner charges and archive-access fees for more predictable, transparent pricing. Your own comparison should start with your invoices and contract language, then use the same partner and document inventory you intend to migrate.
For a CFO or private equity director reviewing several business units, record which entity holds each VAN contract and which routes use it. A shared technical plan does not remove separate notice obligations. For more on that dependency, read our article on EDI VAN exit clauses.
Best practices for approving an EDI migration scope of work
Before anyone signs off, use the scope as a working checklist rather than a description of good intentions. The following review catches omissions that often become urgent only during testing or cutover:
- Make the inventory an attachment that can be updated. Give changes an owner and approval record so everyone knows which partner list is current.
- Distinguish network delivery from business acceptance. Specify how transport, syntax, acknowledgment and internal processing will each be assessed.
- Define the decision for every failed test. Record whether the team will correct and retest, defer a partner from the wave or pause cutover.
- Keep legacy access tied to evidence. State which outstanding documents, acknowledgments and archives must be reviewed before a route or service is retired.
- Match commercial terms to technical scope. Identify charges for partner setup, testing, data access and any overlap with the old contract. Compare the same set of routes and documents in every proposal.
- Record who signs off. An EDI lead can verify message details, but a business owner should also confirm that the workflow is ready to support orders, shipments or invoices.
A good scope makes a switch easier to evaluate. You can see what work you are buying, what might interrupt a transaction and what evidence reduces that risk. That clarity matters when the current VAN is costly: an avoidable billing model should not remain in place solely because the alternative feels too uncertain.
Frequently Asked Questions
What is an EDI migration scope of work?
It is a written agreement defining the partner routes, documents, responsibilities, tests, acceptance criteria, costs and cutover decisions for a move between EDI providers.
Who should approve an EDI migration scope of work?
The EDI lead, relevant IT and application owners and a business owner should review their responsibilities. Finance or procurement should review fees and the existing VAN contract before the scope is approved.
Does a 997 acknowledgment mean a purchase order was accepted?
No. An X12 997 reports whether the document passed the receiver's syntax check and can report acceptance or rejection. It does not confirm that the order or its business content was accepted.
How does dual-VAN reconciliation reduce switching risk?
The old VAN and the new VAN run side by side during migration. Your team compares document records, acknowledgments and control numbers, investigates mismatches and accounts for documents before retiring an old route.
What should happen if a partner fails a migration test?
Record the failed result, assign an owner and agree on a correction and retest. The scope should say whether that partner remains on its old route or the migration wave pauses until the required approval is obtained.
Put the scope in writing before you switch
The decision to leave a costly VAN should rest on a clear plan, not a choice between overpaying and hoping nothing goes wrong. A written scope identifies the work, limits cost surprises and establishes the evidence needed to retire each old route. Dual-VAN reconciliation makes the move low risk by allowing documents to be accounted for while both VANs run side by side.
Compare your current VAN bill with a scoped migration
Bring your partner inventory, current charges and cutover questions. We can discuss how exact kilo-character billing changes the cost comparison and how dual-VAN reconciliation supports a low-risk move to Nexus VAN.
Schedule Demo
