Skip to content
TruePPM

Bring your existing plan in

If your plan already lives somewhere else, you don’t have to retype it. TruePPM reads several source formats as one-way, file-based, point-in-time imports — you upload a file, TruePPM builds a project from it that it can schedule with CPM (Critical Path Method — the algorithm that computes task dates and the critical path), and nothing you import ever writes back to the source. Pick your source below.

Which importer do I want?

Section titled “Which importer do I want?”
Your plan lives in…UseStatusWatch for
Microsoft Project — .xml (MSPDI)MS Project import & exportShipped — REST endpoints since 0.1, in-app wizard since 0.2Constraint dates and actual start/finish dates shipped in 0.4; deadlines, baselines, priority, work and cost are never imported — the import lists what it dropped
Microsoft Project — .mpp (binary)Save as .xml from MS Project insteadShips in 0.6 (#128)As of the 0.4 beta, neither file picker offers .mpp — on 0.3.0-alpha.3 and earlier the import-into-existing dialog still accepted it and then failed in the background worker on any deployment without the optional MPXJ / Java toolchain
A spreadsheet you built by hand, or exported from Asana, Trello, Basecamp, or a similar toolCSV / Excel import & exportShipped in 0.4 — upload, map columns, confirmColumn headers are auto-detected, but always check the mapping before you commit
Jira Server or Data Center (XML issue export)Jira importShipped in 0.4Jira Cloud has no XML export — Cloud has no file this importer can read. Cloud migration is a separate, out-of-scope track
Another TruePPM instance, or a hand-edited file matching the seed schemaData export (JSON seed import)Shipped today, with a dry-run validatorReplace-then-rebuild on the program slug — a colliding program is replaced, not merged, and only its projects are recoverable. Read the re-import semantics before you run it

Not sure which row fits? If the source tool can export a CSV at all, the CSV importer is the safest default — it’s the one built for “a table from somewhere else,” not for one specific tool’s file format.

What none of them import

Section titled “What none of them import”

Regardless of source, a one-way file import is deliberately not a live sync and not a full-fidelity replica:

  • No write-back. TruePPM never authenticates against your source tool and never pushes a change to it. Re-importing the same file again creates new tasks; it does not update the ones you imported before.
  • No baselines, sprints, or board columns. Set these up in TruePPM after the import lands. (An MS Project file’s <Baseline> blocks are read and reported as not imported, not silently dropped — capture a TruePPM baseline once the schedule is in.)
  • No resource rates or capacity. Assignees are matched or created by name; everything else about them stays unset. Working calendars are the exception: the MS Project importer does carry base calendars and their non-working exceptions across.
  • No cost, effort, or deadline fields. TruePPM schedules on duration and dependencies, so Work, Cost and Deadline have nowhere to land.
  • No cross-project dependencies. Every import is scoped to a single project.

See each importer’s own page for the exact list of what it does and doesn’t carry over — the constraints above are the ones every source shares.

Section titled “Related”