1
Inventory the scope
List the workspaces, goals, initiatives, ideas, features, releases, custom fields, automations and owners included in the migration.
Migrate from Aha! without losing the context behind your roadmap.
Before you cancel a license, verify what the Aha! export contains, how records map into WorkThroughLine, and what needs to be archived or rebuilt.
Preview without writes Repeatable import via Reference # Import never deletes data
Pricing and export rules last verified August 28, 2026.Official Aha! pricing Official Aha! export documentation
Controlled exit
Four steps before cutover
The WorkThroughLine importer accepts Aha! list-report CSV files. The safest path is record type by record type, with an untouched source archive and a result check before changing the system of record.
2
Export list reports
Create a list report for each record type, include Name, Type and Reference #, then retain the original CSV or Excel export.
3
Run preflight
Dry run reports records to create or update, unmatched users and row-level errors — without writing data.
4
Import and reconcile
Import goals, initiatives, ideas and features, verify record and link counts, then document what stays archived or needs a manual rebuild.
Actual importer mapping
An Aha! record is not just a generic ticket
The map below reflects the current WorkThroughLine importer, not a marketing assumption. Keep the Reference # column — it is the stable key for repeatable idea, initiative and feature imports.
| Aha! record | WorkThroughLine | What moves | What needs a decision |
|---|---|---|---|
| Goal | Annual goal | Name; initiative-to-goal relationship when available. | Confirm the planning year and advanced strategy fields after import. |
| Initiative | OKR | Name, Reference # for a stable key, and relationship to a goal. | Descriptions, scores, advanced formulas and custom fields are not mapped one-to-one. |
| Idea | Opportunity | Reference #, name, description, status, owner and selected score/votes/tags data. | Portal users, discussions, attachments and non-standard fields need an archive or manual handling. |
| Feature / epic / requirement | Work item | Reference #, name, description, status, owner, creation date, selected metadata and initiative/OKR link. | Release structure, dependencies, attachments, automations and workflow configuration are not reconstructed automatically. |
Cost of waiting
Estimate Aha! list-price exposure over 1 or 3 years
On annual billing, Aha! Roadmaps publicly lists Premium at $59, Enterprise at $99 and Enterprise+ at $149 per paid user per month. Aha! also publishes a 3% annual pricing adjustment. Official Aha! pricing
Aha! Roadmaps TCO calculator
Estimate public list-price exposure before you scope the migration.
Estimated total · 3 years$36,719.89
Starting monthly amount$990.00
- Year 1$11,880.00
- Year 2$12,236.40
- Year 3$12,603.49
Calculator assumptions
Uses public annual-billing prices in USD and applies the published 3% adjustment to every following year. It excludes tax, discounts, implementation, services, other Aha! products and WorkThroughLine pricing. This is a planning estimate, not a quote from Aha! or WorkThroughLine.
Export audit
CSV moves rows. It does not move an operating system.
Aha! states that Excel/CSV export strips formatting from formatted text, including record descriptions and comments. Full account JSON backup is an Enterprise+ capability. Make an explicit decision for every data group before migration. Official Aha! export documentation
Formatting lost
Formatted text
Retain the original export or JSON/HTML source if bold text, lists, tables and links carry evidence.
No 1:1 mapping
Custom tables and worksheets
Export results and document formulas; decide whether each becomes data, a rule or is retired.
Manual decision
Releases and capacity models
Keep historical snapshots; remodel active planning through OKRs, work items and sprints.
Archive
Comments, attachments and portal context
Keep them with the source archive and move only what active decisions still require.
Not imported
Automations, permissions and layouts
Record the owner and purpose of every rule before deciding what genuinely needs rebuilding.
Cutover control
System-of-record date
Agree a freeze, final export, count reconciliation and the date new work starts in WorkThroughLine.
Frequently asked questions about migrating from Aha!
Can WorkThroughLine import Aha! data directly?+
Yes. The current CSV importer supports Aha! goals, initiatives, ideas and features from list-report exports. You can run the import as a no-write preview first.
Is WorkThroughLine a complete Aha! replacement?+
Not for every team. Aha! is a broader enterprise suite with advanced portfolio management, configuration, ideation workflows and reporting. WorkThroughLine is a narrower system for connecting goals, discovery evidence, decisions and delivery.
Why is the Reference # column important?+
The importer uses it as a stable source identity for deduplication and updates. A feature cannot be imported safely without it, and repeat-import quality is weaker when it is absent.
Does CSV preserve description and comment formatting?+
Not fully. Aha! officially states that Excel/CSV export strips formatting from formatted text. Keep the original export or Enterprise+ JSON backup as an archive when formatting matters.
Do all custom fields and automations move?+
No. Supported score, effort, votes, tags, product and release values are retained as migration metadata when present, but custom tables, worksheets, automations, permissions and account configuration have no automatic one-to-one destination.
Is the calculator an Aha! quote?+
No. It is arithmetic based on public annual list prices, the published Discovery Advanced minimum and the published 3% annual adjustment. It excludes tax, discounts, services and contract terms.
Does import delete anything in Aha! or WorkThroughLine?+
No. CSV import reads the export and additively creates or updates supported WorkThroughLine records. It does not access or modify the source Aha! account and does not delete existing WorkThroughLine data.
Aha! → WorkThroughLine
Verify the data first. Change the system of record second.
Create an account, export one representative Aha! list report and run a no-write preflight. You will see the real mapping before you define the cutover.