The Migration Data flow type or business flow is used to transfer P6 project data between two distinct P6 deployments using P6 Export and Import Web Services, or transfer P6 project data to Primavera Cloud.
For example, use this data flow to transfer project data from a P6 on-premises environment to Primavera Cloud environment.
The flow step sequence in the migration data business flow is organized as follows:
- Initialization
This step initializes the projects in the source application before the data is loaded into Gateway. It is available in Project Data flows and Migration Data flows for the following providers only:
- P6 EPPM
- Primavera Cloud
- Unifier
For single project jobs, the Initialization step displays as the first step.
For parent-child jobs, the Initialization step displays for the parent job because the projects need to be initialized before the number of child jobs is determined. It is the only step displayed for the parent job. This step is not displayed for any child jobs. The start and end times of each step is stored in GMT and displays as per your local time.
- Notes:
- “Baseline” Requests / Responses can be suffixed with a number which corresponds to the baselines selected in the relevant parameter. Numbering starts with: 0, 1, 2, 3, etc.
- Primavera Cloud has a hard limit which can cause multiple Request / Responses suffixed with a number. Numbering starts with 1, 2, 3, etc.
The step will only display when the Project Filter within the Business Flow / Synchronization uses an option other than Lookup In <product>.
- Export from Source: This step exports the P6 project data into the Gateway so that it can be processed.
- Update Destination: This step saves the project data into the destination application's database.