Plan the MES exit before the entry

An MES exit plan should establish how production records remain interpretable and how work moves to a replacement or controlled fallback. Agree the deliverables before purchase, when data access and transition support can still be part of the commercial decision.

Define what must survive the application

List production orders, operation results, material relationships, quality decisions, attachments and correction history that the organization needs to retain. Include the reference data and configuration versions needed to interpret them. A table of identifiers is not useful if the meaning of each identifier disappears with the application.

Work with quality, legal and records specialists to determine retention obligations for your products and use. Do not assume one generic MES retention period. Separate operational continuity from historical retention: a replacement system may need open work and active master data, while an archive may need complete historical context. They have different access, security and validation questions.

Test an export before signing

Ask for a representative export from a demonstration environment containing a lot split, a correction, an attachment and a completed order. Have someone outside the supplier’s application reconstruct the relationship between those records using the delivered documentation. Record missing relationships and proprietary dependencies.

Export element	What to inspect
Identifiers	Stable keys and documented relationships
Timestamps	Time zone, event time and correction context
Attachments	Accessible files linked to the right record
Audit context	Actor, reason and previous value where required
Configuration	Version context needed to interpret the event
Documentation	Schema, field meaning and known limitations

This is an acceptance exercise, not a demand that all suppliers use the same file format.

Scope commercial transition support

Ask when exports are available, how long access continues after termination, what assistance costs and what deletion confirmation is provided. Determine whether a read-only archive requires continuing licenses. Review the contract with qualified counsel and procurement; a technical export demonstration does not establish the legal right to use or retain every component.

Define responsibilities if the supplier changes ownership, discontinues a product or ends a service. A generic promise of cooperation is weaker than named deliverables and access windows. Keep transition assumptions in the ownership cost model. Do not claim to know the future cost of migration; use a clearly labeled allowance and revise it when scope becomes concrete.

Plan the open-work cutover

Historical records can often be handled separately from work in progress. For open orders, decide whether to finish them in the old system, transfer them with a controlled reconciliation or restart under an approved procedure. Each choice affects material balances, quality status and operator instructions. Test the method using a fictional order before a production cutover.

Freeze and reconcile master-data changes during the agreed window. Record the last accepted event in the old system and the first in the new one. Preserve a rollback decision point and an owner. Do not assume that importing a database backup into a different product creates a meaningful execution state.

Preserve access without creating a security gap

An archive still needs access control, backup, monitoring and a tested restore process. Identify who can retrieve records after the project team is gone. Document any software or operating environment required to read proprietary formats and assess how that dependency will be maintained.

Use representative retrieval tests, including records with attachments and corrections. Check that authorized staff can answer a production or quality question within the organization’s required time. Restrict write access to historical records according to the approved process. Keeping an old server powered on indefinitely without an operating owner is not a complete records strategy and may create an avoidable support burden.

Revisit exit readiness during operation

Schedule a review when the system changes materially, such as a new module, site or record type. Update the export inventory and confirm that the current version still produces usable data. A successful export at purchase time does not prove that later customizations are covered.

Retain the exit plan with architecture and support documentation. Include owners, contract references, recovery dependencies, open-work strategy, archive access and known gaps. An illustrative planning milestone is to complete a retrieval exercise before renewal discussions; the timing is a buyer choice rather than a universal requirement. The goal is to keep transition a manageable engineering task rather than an emergency discovery exercise.

FAQ

Is a database backup an exit plan?

A backup supports recovery into a compatible environment. Exit also requires interpretable data, access rights and a transition process.

Must all history move into the new MES?

Not necessarily. Determine operational and retention needs, then assess whether a controlled archive is appropriate.

When should export be tested?

Before purchase if possible, and again after material changes. Use records with relationships and exceptions rather than a simple flat list.

Continue your decision

Use the mes ownership cost to document your own inputs. Compare operating models on the comparison page.

Sources and scope

NIST SP 800-82 Rev. 3 — Official OT security guidance. The page distinguishes the final revision from newer draft work; check status before use. Our test scenarios are editorial examples.

Examples are hypothetical and are not measured customer results, supplier quotations, or evidence of professional review. Prepared on October 30, 2026; confirm current requirements with the relevant official body and your responsible specialists.