Identify the backup before restoring
A planning JSON backup preserves spheres and planning metadata. It does not recover account identity, billing, sessions or provider credentials. Before importing it, distinguish that file from the account-data export available at /account. An ICS file is not a substitute for a planning backup either.
Ora’s .ics import brings in calendar events through a preview and does not maintain synchronization. That is a calendar operation; use the planning JSON backup flow to review restoration of spheres and their relationships.
This walkthrough prepares a review; it does not report a completed restoration. Use fictional data in a rehearsal and retain the original file separately.
Two JSON files answer different questions
Question one: “Do I want to load my plans again?” The versioned planning backup offers a validated preview and requires explicit replacement. Restoration assigns fresh identifiers while retaining structural references. Do not treat it as an operation that simply adds everything to the current plan.
Question two: “Do I want a copy of my account data?” Account export is available on Free and Pro and excludes credentials and signed billing links. That purpose does not automatically make its output importable by the planning restore flow. Use the workflow specified for each file type.
Prepare a small, observable check
Imagine a fictional sphere with “Prepare materials” and “Review list,” each with a note. If you define a dependency in the plan, record which should follow which. These are authored examples, not exported Ora records.
- Before importing, identify the file type and preserve a copy of the state you want to protect.
- Read the preview: compare the expected spheres and relationships before accepting replacement. If something differs, stop and review the file.
- After a restoration you explicitly choose, compare names, notes and relationships rather than requiring old identifiers to match.
- Check account access through its normal flow. Planning JSON does not replace sign-in or restore an external connection.
A backup does not guarantee every kind of recovery
Ora also documents an optional per-account local copy, off by default, subject to browser-storage limits. Do not confuse that option with a file you have exported and retained yourself. Having a file does not establish that you have rehearsed its restoration.
Consulted on 24 October 2026, Todoist explains its backups and Things its data-export workflow. These help compare what each system retains and how it restores it; they do not establish that their files are interchangeable with Ora.
Check the scope before choosing the next step
Ora’s public reference separates planning backups, account export and external connections. Review that scope before saving or importing a file. The demo lets you explore planning without registration; its changes stay in that tab and do not establish real-account recovery.