Import brings an existing schedule into a Syncify project. It is usually the fastest way to begin a review without rebuilding the WBS and activity network.

Choose a file format

P6 XML/PMXML is not supported. If you see broad “XML” wording in the file picker, use XER for P6 and MSPDI XML for Microsoft Project. Renaming an extension does not convert a file.

Import does not reproduce every source application feature. Review P6 compatibility or Microsoft Project compatibility for omitted fields, calendar differences, and scheduling behavior. Microsoft Project exports from Syncify are not available; export options include PDF, Excel, and XER.

1. Choose the destination

Open the project’s Files page and select Import. You can also choose Import schedule from Home, select the destination project, and continue to the file wizard.

Confirm the project before choosing files. Multiple P6 projects in one XER become separate schedules within the selected Syncify project; they do not automatically create separate Syncify projects.

2. Upload and review the source

Choose or drop the source files into the wizard. Review the parsed schedules, names, IDs, status dates, and any warnings. Select the schedules you want to bring in.

Pay particular attention to warnings about external relationships and Microsoft Project summary-task relationships. A relationship whose endpoints cannot be represented in the imported schedule will not provide scheduling logic afterward.

If parsing fails, use the original file format exported by the source application. For an unsupported or password-protected MPP, try an unprotected MSPDI XML export. For a calendar error, check the named calendar in the source file before trying again.

3. Import a new file or replace an existing schedule

Import as a new schedule to preserve the previous submission and compare the two. Give it a clear name and ID, and choose a folder if offered.

Use Replace only when you intend to update an existing target schedule in place. Select the correct target for each incoming schedule and review the mapping. The target retains its existing name and ID. Preserve a version or copy first if its previous state is important.

For recurring submissions, keeping each issued update as its own schedule or version makes the reporting history easier to audit.

4. Choose custom columns

When the source includes supported P6 activity codes or user-defined fields, select the columns you need. Map a source field to an existing project column when it represents the same information. For example, map a contractor’s “Area” code to the project’s established Area column rather than creating a second, nearly identical field.

Check the type and meaning before mapping. A cost value, a date, and a text label should not be treated as interchangeable just because their titles look similar. Standard activity fields do not need to be recreated as custom columns.

5. Carry over Syncify-only information

The Copy Over Columns step can carry selected columns from a reference schedule into the incoming schedules. Use this for information entered in Syncify that is not maintained in the source file, such as review notes or a responsibility field.

Choose the reference, destination schedules, and columns deliberately. This depends on matching activities across schedules; renamed or replaced activity identities may not match as expected. Spot-check the result, especially if the source’s activity IDs have changed.

The step may be unavailable or have nothing to copy for a particular import. It is not a substitute for importing source fields or for reviewing all changes.

6. Finish and verify

Choose Import or Import & open. From the completion screen, open the schedule or return to the project.

Before relying on the result:

1. Check the WBS, activity count, milestone types, and recognizable activity IDs.
2. Review the status date, calendar workweek, exceptions, and assigned calendars.
3. Check actual starts/finishes, remaining durations, and percent complete on progressed work.
4. Review the relationships and import warnings.
5. Check a sample of custom fields and resource assignments you expected to retain.
6. Compare the imported start and finish with the source before choosing to recalculate.

An imported P6 schedule starts locked. Unlock only when you intend to edit or calculate it. Recalculation uses Syncify’s calculation settings and can legitimately change source forecast dates; it does not rewrite historical actuals to make the imported forecast match.

Finally, use Files to set Current, Baseline, or Update # as appropriate. These project reporting designations are separate from the import itself.

A useful monthly-import routine

Import the new submission as a separate schedule, carry over the review columns you need, check the warnings and key dates, assign its update number, and compare it with the prior issue. Make it Current when the team is ready to use it. Keep the approved baseline designation on the agreed reference file.