Upgrade notes
Projetex 7D is designed to install alongside Projetex 5D so you can validate the new installation before retiring the previous one.
Recommended path from Projetex 5D
Section titled “Recommended path from Projetex 5D”- Create a fresh backup of the Projetex 5D database.
- Install the current Projetex Server separately from the 5D server installation.
- Restore the 5D backup into Projetex 7D.
- Install or update the Projetex Workstations that will connect to the new server.
- Verify the agency data and day-to-day workflow before you stop using the older installation.
A Projetex 5D backup can be restored directly into Projetex 7D.
Clean database or existing data
Section titled “Clean database or existing data”Current Server setup distinguishes between starting with a clean database and moving data from a previous installation.
When the Get Data upgrade path is selected, Setup records the upgrade intent and hands the migration work to the Projetex Upgrade Utility. A clean-database installation does not start that migration handoff.
Large restore/conversion work is intentionally kept out of the setup wizard so it can be handled by the dedicated migration process.
Older Projetex generations
Section titled “Older Projetex generations”The current release includes the Database Converter required for supported older-database migration scenarios.
Do not rely on instructions from an older CHM or a retired installer when moving production data.
What happens to machine-specific settings
Section titled “What happens to machine-specific settings”After a supported restore/migration, Projetex clears machine-specific registration and file-storage settings from the source installation instead of silently inheriting them on the new server.
Recheck server, file-storage, registration, and workstation connection settings after migration.
Cross-product migration
Section titled “Cross-product migration”Current 7D database migration support also allows supported backup/restore movement between TO3000 and Projetex 7D. This provides a path when a one-person workflow grows into an agency workflow, or when data needs to move in the opposite direction.
Always verify the resulting database and application-specific settings before using the migrated copy as the only production system.