Data Migration Checklist for Oracle Primavera Unifier
A migration execution outline for sequencing extraction, transformation, load and reconciliation.
Overview
One of the primary requirements while implementing Primavera Unifier is migration of data from an existing system into Primavera Unifier. This blog provides a basic outline and approach to handle such migration requirements.
Pre-migration
Some of the most common scenarios are where a customer is already managing projects in an ERP/legacy system. This system tends to have project information, purchase orders, invoices, etc. for existing projects, as well as some inactive projects. Below are some basic points to keep in mind before migration:
- Define what needs to be migrated. This will help you map each object to the respective Forms and Business Processes within Unifier.
- Does the source system support REST APIs, or will it be a file-based migration?
- Data variation and validation — for example, date formats, currency fields, whether exchange rates are defined, and so on.
- How do you want to migrate data? Is there any sequencing involved? How will you handle retries and error handling?
- Identify master data dependencies such as users, companies, CBS/Cost codes, uDesigner configuration, and any data pickers used in forms/BPs.
- Define a reconciliation method upfront (record counts, key totals, sampling, and how exceptions will be tracked and resolved).
Migration
If there is inactive project data, it’s a blessing in disguise—always migrate it first to iron out runtime errors and issues. After migrating inactive projects, migrate active project data.
A couple of additional points to keep in mind during execution:
- Maintain a repeatable runbook (dry runs, versioned mapping sheet, repeatable scripts, and a rollback approach if needed).
- Decide how to handle attachments and linked records (for example PO ↔ Invoice ↔ Payment relationships, or any linked BPs/records that need consistent sequencing).
Post-migration
Write reports to extract records from Unifier and match them against the source system to ensure data is mapped correctly.
if migrated Business Processes require workflow, use a simple two-step workflow during migration runs so verification and approvals stay controlled.
Also consider preparing a sign-off pack that includes reconciliation results (counts/totals), exceptions, known gaps, and a clear note on what was not migrated.