Bringing a plan from Microsoft Project requires checking how activities and relationships are recognized. Importing is a step to check, especially when updating an existing project.
Import a Microsoft Project plan
- Open Import MS Project in the intended MS Project Planning project or context. Check the recipient before choosing the file.
- Use a supported MPP file and respect the upload limit. The application checks the extension, binary structure and readability of the content.
- A technically readable MPP may not contain the mandatory custom fields required by Orchestris. Check templates and messages before continuing.
- Examine the outcome or preview and confirm only after verifying data and context. Don’t confuse uploading the file with completing the import.
Confirm import and MPP updates
- After uploading, read the outcome of the import and any reports. Keep the original file so you can compare the result.
- Check task hierarchy, dates, work, progress and dependencies. Custom field business conventions must be respected.
- When the function proposes updates, it checks the perimeter and confirms from the provided form. Don’t blindly repeat a submission due to a simple doubt about the outcome.
- Open the resulting plan and compare a sample of tasks with the original. Report differences using identifiers and messages, avoiding sensitive data.
Putting this into practice
Before confirming, read the summary and check the elements involved. After the operation, compare the main parts of the plan with the starting reference.
Learn more about Orchestris.
Comments and questions
Do you have a question about this topic? Open the discussion with a comment.