List what continuity requires
Before changing systems, identify the tasks, open decisions, dependencies, recurrence rules and approved context references that must remain understandable. A flat task list may omit relationships even when every title is present. Decide which history matters for the next action and which belongs in another authorized record system.
Read the export scope carefully
Nifty’s older help describes completed-task reporting from Workloads. That is a particular report, not proof that a full workspace can be restored elsewhere. Verify current export formats and scope in the actual account before relying on them. Do not equate a successful download with a usable migration or backup.
Use a small fictional fixture
Create or use an authorized harmless sample containing a blocker, an unfinished occurrence, a comment and a linked context reference. Compare what the export preserves with the required record. Note omitted fields and links that require continued account access. A row-count match cannot establish that the receiving tool understands the relationships.
Keep a reversible transition
Do not cancel access or remove the old record until the responsible people accept the new workflow and retention needs are addressed. Avoid running two active sources of truth indefinitely. Agree the cutover, the remaining read-only reference period and the owner of unresolved gaps. This guide does not perform cancellation, deletion or data transfer.
Compare relationships as well as rows
For the fictional fixture, list the expected task references, dependency direction, recurrence meaning, open decision and context location before export. Inspect each after the export and again in any proposed receiving process. A file can preserve text while losing the behavior that made it useful. Record those losses and any manual reconstruction needed. Keep the old access arrangement until the responsible owner accepts the evidence and confirms the remaining retention requirements.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Nifty completed-task reports — Merchant documentation · help.niftypm.com · Merchant-controlled · checked 2026-10-01
- Nifty task, subtask and milestone dependencies — Merchant documentation · help.niftypm.com · Merchant-controlled · checked 2026-10-01