⌘K · Import · Shortcut
via the import wizard
- ✓ lands on the spine, joined to accounts
- ✓ one-way — read-only on Shortcut
- ✓ free on every plan
Token used once · not stored
Migrate from Shortcut — import in minutes.
Your stories come across with their workflow state. Bugs stay bugs, completed work stays done, and each story joins the customer behind it.
Free · the token is used once and never stored.
Shortcut tracks engineering work as stories moving through workflows. The stories know their state. They do not know the accounts or the revenue behind them, so the backlog reads as a queue rather than as demand.
Imported onto the spine, each story becomes a backlog item joined to the customer evidence that justified it.
What comes across
Bringing Shortcut onto the spine
-
Stories become backlog items
Features and chores land as tasks, bugs land as bugs, with state mapped to open, active or closed.
-
History included
The full non-archived backlog comes across, so the board is not empty on day one.
-
Three steps, one token
Pick Shortcut, paste your API token, import. The token is used once and never stored.
FAQ
Migrating from Shortcut
How long does a Shortcut import take?
Minutes for most teams. Stories stream into AIOProductOS with their workflow state mapped to open, active or closed, and bugs stay typed as bugs.
Is anything written back to Shortcut?
No. The import is one-way and read-only on the source, and the token is used once and never stored.
Is it free?
Yes. Importing your own history is free on every AIOProductOS plan.
Start full, not empty.
Bring your Shortcut history onto one record per customer — revenue, feedback, work, and code, joined. Free on every plan.