Legacy FDT Migration and Compatibility Solution
Legacy FDT Migration and Compatibility addresses the primary problem of continuing, upgrading, or migrating legacy FDT / DTM / host assets. This page helps readers decide whether to enter this solution package; it does not replace a project solution or product specification.
Primary product anchor: fdtSERVER.
Value
The value of following the “Legacy FDT Migration and Compatibility” solution path is to place legacy FDT, hosts, device assets, editions, licensing, and maintenance windows into an inventory-based migration assessment path before promising a migration result.
For brownfield project teams and system integrators, this solution page should help readers determine which assets need inventory, which questions should move to the fdtSERVER product page or compatibility/migration checklist, and which conclusions must wait for site assessment and completed evidence.
Migration duration, downtime windows, rollback results, third-party defect responsibility, and specific interface boundaries are not commitments made on this page; confirm them in specifications, migration assessments, or project-level materials.
For whom
| Role | Typical question |
|---|---|
| Existing device integration customers | Existing FDT / DTM / Frame assets need to be assessed for continued support |
| System integrators | FDT capabilities need to be integrated into a new system through Web APIs |
| Plant owners / operations | Maintenance windows, asset inventories, licensing conditions, and risk boundaries need to be assessed first |
Composition
- Primary product anchor:
fdtSERVER. - Supporting products: determined by the target devices, existing assets, protocols, hosts, and validation objectives.
- Resource handoff: product pages, specification index, FAQ, PoC preparation checklist, compatibility/migration checklist, and security and permission audit guidance.
Validation path
- Provide the target devices, protocols, existing hosts / Frames / systems, runtime environment, and security requirements.
- Select representative devices or representative assets for a limited-scope PoC according to the solution package.
- Output applicable / non-applicable boundaries, missing facts, and topics for the next technical discussion.
Key boundary table
| Assessment item | Discussable facts as of 2026-07-09 | Boundary to retain |
|---|---|---|
| Cross-Platform | Cross-Platform Edition is limited to FDT 3.0 and Linux scenarios adapted for .NET 6 | Does not cover FDT 1.2.x / 2.x DTMs |
| Migration result | Can proceed to asset inventory, representative-device validation, and migration assessment | Does not promise a fixed migration duration, downtime window, or rollback result |
Applicability
- Suitable for solution definition, early technical assessment, and standardized PoC preparation.
- Suitable for confirming devices, protocols, hosts, runtime environments, permissions, and responsibility boundaries before clarifying project scope.
- Unauthorized cases or quantitative results must not be introduced.
Exclusions
- Not a quotation, project schedule, implementation plan, acceptance criterion, or contract attachment.
- Does not promise unconfirmed compatibility, performance capacity, quantified customer results, or unconfirmed routes.
- Does not describe device integration as an end-to-end business system.
Next Step
View the fdtSERVER product pageDownload the compatibility/migration checklist and inventory FDT / DTM assetsView the Product Center Resource Center