How to upgrade Primavera to 25.12 while preserving data

What should you know before installing?

Record the connection alias shown on the P6 login screen. In Database Configuration, identify the driver and the database file or server. Standalone installations commonly use SQLite; shared installations may use Oracle or SQL Server. Record the P6 version, database location, connection alias, username and Windows version. Store your backup separately from the working database.

1. Full backup for standalone SQLite

1. Export important projects to XER and, where needed, XML. Export personal layouts separately and retain essential reports and settings.
2. Read the actual database file path from the connection settings. The filename is not necessarily P6Standalone.db; do not guess its location.
3. Close P6, Visualizer and any process accessing the database, then make a complete, dated copy of the database file. If the database remains open or uses a write-ahead log, use a SQLite-compatible backup method. Copying a file while it is being written is unreliable.
4. Do not only store the backup: open a test copy with the current software version and verify that the projects are present. Keep the original backup untouched.

2. Install and connect to existing data

Check the source version, target version and operating system against Oracle’s Tested Configurations and installation guide. Older or 32-bit installations may require a different upgrade path or an intermediate step.

1. Extract the 25.12 installation package locally and use a trusted installer. Complete this step in a test environment first.
2. In Database Configuration, select the driver P6 Pro Standalone (SQLite) .
3. Connect to the previous data. Add a Connection to an Existing Standalone Database and browse to the test copy of your database. Creating a new database does not automatically transfer your existing projects.
4. On first launch, P6 may report a mismatch between the application and database versions and request a schema upgrade. Approve it only after verifying your backup. The installer is not a substitute for a backup.
5. After validating the test, schedule the production upgrade, disconnect users, take a fresh backup and repeat the verified procedure.

3. Verify the results before returning to work

If your projects are not visible

Check the connection alias, database path, selected EPS and project filters first. You may be connected to a new, empty database. Do not delete the original files. To roll back, connect a compatible older client to a copy of the pre-upgrade backup; do not force an upgraded database to open in an older client.

Oracle & SQL Server installations

Shared databases require a full DBMS backup, a restore test, compatible client/server versions, administrator approval, a connection shutdown plan and a rollback plan. The SQLite procedure alone is insufficient. Migrating an older Oracle XE or SQL Express database to SQLite is a separate operation.

Free Project360 Persian add-on

This Windows tool is produced and delivered by the Project360 team for free and only for Primavera P6 Professional 25.12 . The supplied file/installer password is project360 . Check your P6 version under Help → About before installing the tool. Compatibility with other versions is not claimed.

Our goal is to promote professional updating: the conscious use of new versions, after reviewing compatibility and backup, is part of engineering discipline and quality of planning work. 25.12 version is the target of this tool; the title of “the last version” with time should be reviewed again.

Free is related to the Project360 tool; the license and terms of use of the Oracle software are independent.

Frequently asked questions

Sources & review date

Review: October 21, 2026. the basis of the SQLite route is the official P6 Professional Version 25 independent installation and configuration guide, section Upgrading with a SQLite Database.