Migration
Bring your work across
Browser-based planning tools keep everything in local storage, which is fragile, because clearing site data destroys it, so most of them offer an export button. Throughline imports that export.
The supported format
A single JSON document containing a cards array of videos and a channels array, where each card carries its own research, script, SEO, thumbnail and social-post fields.
The file is matched on shape, not on which tool wrote it, so any export following that structure will import.
What to do
- 1Export your data from your current tool as a .json backup and keep the file somewhere safe.
- 2Create a Throughline account, then go to Settings → Legacy import.
- 3Upload the file. You get a full preview of every brand and project it would create, before anything is written.
- 4Apply the import and read the migration report. If it is not what you wanted, roll it back in one click.
Claims arrive unverified, on purpose
Local planning tools generally do not record where a fact came from, so nothing imported can honestly be marked as sourced. Every imported claim lands as UNVERIFIED with a note saying why. Attach sources before you lean on them again.
What maps to what
| Legacy field | Throughline | Notes |
|---|---|---|
| Channel | Brand | Name, niche, audience, voice, accent colour and social handles. |
| Video card | Project | Title, tags, archive state, publish date and target duration. |
| Board column | Stage | Research → Research, Script/Audio → Script, Visual → Production, Thumbnail/Meta → Packaging, Publish → Review. |
| Final brief | Brief | Angle, USP, emotion, transformation, narrative and CTA map onto the new brief fields. |
| Foundation | Brief + notes | Audience, awareness stage, problem, outcome and curiosity. |
| Ingredients: evidence | Claims | Each line becomes a claim, marked unverified with no source. |
| Hooks list | Hook options | Including which ones were starred. |
| Title variants | Title options | One per line. |
| Script parts | Script v1 | Each part becomes a section, in order, as version 1. |
| SEO fields | Packaging | Description, tags, chapters, pinned comment and end screen. |
| Thumbnail fields | Thumbnail brief | Concept, overlay text and image prompt, combined. |
| Social posts | Repurpose assets | Platform, caption, hashtags, schedule and live URL. |
| Transcripts and scratch notes | Research notes | Preserved verbatim rather than discarded. |
What does not come across
- Reference images. These usually live in the browser's own storage and are not included in the export file. Re-upload the ones you still need.
- Custom prompt overrides and visual presets. The prompt system here is versioned and server-side, so per-project prompt edits have no equivalent. Custom visual styles can be recreated as workspace-level styles that your whole team can use.
- Local drive folder links. These are browser-local file handles and cannot be transferred.
- Search history and tool-internal logs. Not user content.
Limits and safety
- Maximum file size 25 MB, maximum 2,000 videos per import.
- The file is validated before anything is written. A malformed file is rejected, not partially applied.
- Nothing you already have is modified or deleted. An import only ever adds.
- If your plan's project limit is lower than the number imported, the extras arrive archived rather than being dropped, and you choose what to reactivate.
- The original file is kept so an import can be rolled back or investigated.