Import your data

Most projects don’t start from zero — you already have a risk log, an actions list, a stakeholder map. Onboarding lets you seed those registers so the project is useful on day one, without waiting for new communications to arrive.

Find it under a project’s Settings → Import data, or from the prompt on the project Overview until the project has data.

The onboarding steps

1. Choose a methodology — PMBOK, ISO 19650, or Agile. This decides which documents the project can generate. You can switch it later.
2. Connect your inputs — link email, Slack, ClickUp and so on (see Connecting your tools).
3. Seed your registers — paste or upload your existing data.
4. Add documents — generate the deliverables for your methodology.

Seeding registers

You can seed every register — risks, issues, decisions, actions, stakeholders, and more — from structured Markdown, CSV, or pasted text. The flow is always preview, then commit, so you see exactly what will be created before anything is written.

A few things worth knowing:

• It’s idempotent. Importing the same data twice won’t create duplicates — rows are matched on a natural key (such as a code, or an owner’s email).
• Owners become stakeholders. When an action lists an owner’s email, that person is created as a stakeholder automatically and linked to the action.
• Seeded items are first-class. They go through the same services as everything else, so they’re part of the graph and identity model immediately — future emails will link to them.

Retiring stale history

When you import years of old history, it’s valuable for the knowledge graph but can flood your work surfaces with items that are no longer live. ddx PMO can retire stale imported items — archiving them with a reason rather than deleting them — so they stop being noise while staying fully in the record. A retired item reads differently from one you archived by hand, so you can always tell why something is out of the way.