PDM MIGRATION CHECKLIST
PDM Migration Checklist: Versions, Database, Vault, Licensing and Rollback
A practical PDM server migration checklist covering compatibility, databases, vaults, licenses, customizations, backups, testing and rollback.
Answer first
A PDM migration is more than copying a database and vault. Inventory application versions, databases, file stores, licenses, jobs, service accounts, DNS, certificates and customizations, then prove restoration, rehearse the cutover and define rollback conditions.
Environment and compatibility
- PDM/PLM server, clients, CAD integrations and database versions.
- Operating system, domain, service accounts and runtime dependencies.
- License server, license files and vendor support status.
- Custom code, jobs, reports, APIs, batch output and external interfaces.
Data and backup
- Full database backup with a proven restore.
- Vault or archive capacity, file count and consistency.
- Attachments, indexes, logs and required configuration.
- Transaction freeze and delta-synchronization method.
Rehearse before cutover
Restore the complete environment in isolation and test representative users, data and workflows. Use the rehearsal to estimate the production outage.
- Document steps, owners and checkpoints.
- Define go/no-go times and criteria.
- Keep a controlled rollback path.
- Confirm DNS, certificates, firewalls, mail and schedules.
Post-migration acceptance
- Compare record, file, revision and relationship samples.
- Test role-based login, search, download, edit and approval.
- Validate CAD integration, BOMs, jobs, reports and interfaces.
- Verify performance, logs, backups, alerts and administrator SOPs.
Frequently asked questions
Must a PDM migration include a version upgrade?
No. Combining migration and upgrade increases variables; decide based on compatibility, outage, vendor support and test capacity.
Is a successful backup enough?
No. Restore the backup in isolation and test the database, vault, permissions, customizations and external interfaces.
When can the old server be retired?
After acceptance and the agreed rollback period. Keep a controlled read-only or recoverable state when required.