Skip to content

Read the import fidelity report

All plans Project Member

Before you can trust a migrated plan you have to answer one question: did all of it arrive? A preview tells you what a file contains before you commit. This tells you what actually landed afterwards, and it does it in a form you can file with the project.

Every wizard import, from a file or from Project Online, produces an Import fidelity report: a PDF placed in the project’s Project Documents library, alongside a table you can read on screen.

Three routes to the same thing:

  • The amber banner at the top of a freshly imported project, which reads “Open the fidelity report (94% of the source landed)” once the percentage is known.
  • View full import details on that banner, or Show import details from the project’s menu, which opens the table without leaving the page.
  • The Import complete notification, in the app and by email.

One row per kind of thing, with what the source carried, what was committed, and the difference:

  • Tasks, summary tasks and milestones
  • Dependencies, broken out by all four types, so a plan that lost only its start-to-start links says exactly that
  • Tasks with an assignee, and resources matched to workspace users
  • Custom field definitions and custom field values
  • Tasks with a baseline cost, and with a planned cost
  • Tasks with a constraint, and with a deadline

Warnings and errors from the import are counted on the report too.

The fidelity percentage is the share of countable source elements that landed. The verdict is stricter than the percentage: an import is complete only if every countable row landed everything, and partial if any one of them came up short. A 99% import is still partial, which is the honest answer, because the missing 1% is somebody’s dependency chain.

When the source carried nothing countable, the report says so rather than showing a zero.

Resources sit outside the percentage on purpose. A resource your workspace has no user for is a mapping gap, not lost schedule data: the task and its dates arrived intact, and somebody just needs inviting. Counting it would mark a clean 2,000 task import as partial because one contractor’s address is not a member yet.

They still get their own row, with how many were unmatched and how many came through as a name with no email, so the gap is visible without distorting the headline.

The PDF carries a SHA-256 fingerprint of its own counts, and the same fingerprint is stored on the import record. So a PDF someone emails you months later can be checked against what Onplana recorded at the time: the same import always produces the same fingerprint, and one changed number changes it.

That is what makes the filed copy evidence rather than a printout.

A project that has reached its file limit does not get the PDF. The counts are still there in the import details table, and a warning says why the document is missing, so nothing about the import itself is lost. Clear some space in the project’s documents and re-run the import if you want the filed copy.

Where exactly does the PDF go? The project’s Project Documents library, the same automatic library that collects task attachments. See Organize project files in document folders.

My import says partial but nothing looks missing. Read the rows rather than the headline. Partial means at least one countable row came up short, and it is often custom field values rather than tasks. The row names which.

Can I get one for an import I ran before this shipped? No. The report is produced at import time from counts taken during the commit, so it cannot be reconstructed afterwards. Re-importing a file produces one.

Does an unmatched resource mean I lost data? No. The task, its dates and its structure all arrived. What is missing is a workspace user to assign it to, which you fix by inviting them and assigning the tasks.