Migrating between scheduling platforms is one of the biggest headaches for planners. In this article we explain the exact steps, what is preserved automatically, what you need to verify and how TecnoAdmin's Converter can do the process in seconds.
Why migrate from MS Project to Primavera P6?
MS Project is excellent for individual projects and small teams. But when a project grows in complexity (multiple work fronts, thousands of activities, multi-project resource control, executive reporting), Primavera P6 offers capabilities that MS Project does not have.
The most common migration cases are:
- The client or the supervising engineer requires delivery in Primavera P6 format (.xer)
- The project grows and MS Project starts to become slow or unwieldy
- You need to consolidate multiple projects into a single database
- The controls team needs more robust EVM indicators
Important note: The conversion is never 100% perfect. There is always a difference in how each software handles calendars, complex "Lag and Lead" type relationships or resource data. Always verify the result before using the converted schedule as the official baseline.
What is preserved in the conversion
| Element | MS Project (.mpp) | Primavera P6 (.xer) | Status |
|---|---|---|---|
| Activities and names | Tasks | Activities | ✓ Complete |
| Durations | Duration | Original Duration | ✓ Complete |
| Relationships (FS, SS, FF, SF) | Predecessors | Relationships | ✓ Complete |
| Planned dates | Start/Finish | Planned Start/Finish | ✓ Complete |
| Baseline | Baseline | Project Baseline | ⚠ Verify |
| Calendars | Project Calendar | Calendars | ⚠ Verify |
| Resources and costs | Resources | Resources | ⚠ Partial |
| WBS | Outline levels | WBS | ✓ Complete |
| Notes / memos | Notes | Activity Notes | ⚠ Partial |
| Custom fields | Custom fields | User Defined Fields | ✗ Manual |
Step-by-step migration process
Clean up the MS Project file before converting
Remove empty tasks, fix circular relationships, verify that all activities have a duration greater than zero and save the file in .mpp format (not .xml). A dirty file produces a dirty conversion.
Verify the WBS structure
Primavera P6 handles the WBS more strictly than MS Project. Make sure your summary/detail hierarchy is consistent. Summary tasks in MS Project become WBS nodes in P6.
Convert with TecnoAdmin's Converter
Upload the .mpp file at productos.tecnoadminconsulting.com, select "MS Project → Primavera P6" and download the resulting .xer. The process takes less than 10 seconds for projects of up to 5,000 activities.
Import the .xer into Primavera P6 and verify
File → Import → XER File. Once imported, review: the total number of activities, WBS integrity, calendars, baseline and the critical path. Compare the total project duration against the original.
Reconfigure calendars and resources
Calendars often need manual adjustment, especially if you use calendars with national holidays. Resources are imported but their cost assignment may need review.
Practical tip: After importing, run a schedule (F9 in P6) and compare the project's Finish Date with the original in MS Project. If there is a difference greater than 1 week, check the calendars: that is usually where the problem is.
Common errors and how to avoid them
Error 1: Durations change on import
Cause: a calendar difference between MS Project (8-hour working days) and Primavera P6 (configurable). Solution: verify that the calendars in P6 match those in MS Project exactly on daily hours, working days and holidays.
Error 2: The critical path disappears or changes
Cause: Primavera P6 does not use the same CPM algorithm as MS Project. Solution: run a Schedule Check (Project → Schedule → Schedule Options) to identify activities with hard constraints that are forcing dates.
Error 3: The baseline does not import correctly
Cause: MS Project uses a single main baseline while P6 supports up to 50. Solution: after importing, manually create a new Baseline in P6 and assign it as the project's Baseline 1.
What about the reverse conversion (P6 → MS Project)?
The reverse process works just as well with the Converter. It is more common when the client or the end client requires the schedule in MS Project but you work in P6. In that case, you export the .xer from P6, upload it to the Converter and obtain the .mpp in seconds.