Stack replacement

Replacing the stack you already pay for

Every plan here says which of your tools has an importer, which has a connector, and which has neither.

What the move costs

Replacing a work stack means moving docs, tasks and team chat out of separate per-seat products into one workspace. Polaris holds all three for free and adds AI workers billed at roughly two dollars per human-hour delivered. Notion, Slack, Linear and GitHub can be connected instead of migrated. Jira, Confluence, Asana, Trello, ClickUp, Monday and Airtable have no connector, so those need an export and a rebuild.

Combinations covered: 18
Tools with an importer: Notion only
Tools you can connect instead: Slack, Notion, Linear, GitHub
Polaris software: $0, no seats

Why these pages exist

Most migration content is written by the company that wants you to migrate, which is why it never mentions the parts that do not move. These pages do. Each one names the specific handoffs your combination is losing work in, then tells you which parts of the move are an export, which are a rebuild by hand, and which are not worth doing at all.

The set is organised by what teams actually run rather than by tool. A team on Confluence and Jira has admins, space permissions and a compliance answer to give. A team on Trello and Slack has none of that and a much smaller bill. The same advice would be wrong for both.

The two honest verdicts

Not every combination should be replaced wholesale, and saying so is the point.

Connect, keep, retire the rest

Your stack is mostly Notion, Slack, Linear or GitHub
Those four are in the Polaris connection catalog, authorised once for the whole org
AI workers read them through the connection with no export at all
You retire the per-seat products that are not in that list first

Export and rebuild

Your tracker is Jira, Asana, Trello, ClickUp, Monday or Airtable
None has a Polaris importer and none is in the connection catalog
The realistic move is a CSV export plus a rebuild of the lanes you still use
Most teams find the rebuild smaller than expected because half the board was dead

What every plan on this page covers

The seam
The specific handoff between your tools where work goes missing. Between a Notion spec and a Jira ticket it is the decision that changed after the spec was written. Between anything and Slack it is scrollback.
The three-way sort
What consolidates cleanly, what arrives with something missing, and what does not transfer at all. Relational data, automation rules and permission models are usually in the third category.
The staged plan
Stages you can stop after. Every plan puts new work in Polaris before it touches history, so an abandoned migration still leaves you somewhere sensible.
The bill, before and after
Per-seat subscriptions multiplied by headcount today, against free software plus metered delivery afterwards. The arithmetic lives on the cost pages, which quote real list prices with the date they were checked.

Every stack combination

Eighteen plans. Find the one that matches what you are paying for now.

Replacing Notion and Jira

The spec lives in one product, the work lives in another, and the two stop agreeing about four days in.

Replacing Notion and Slack

A stack with a writing tool and a talking tool, and no place where a piece of work has an owner and a date.

Replacing Jira and Slack

Engineering teams on Jira and Slack have a tracker, a chat tool, and specs living in ticket descriptions.

Replacing Linear and Notion

Two tools people choose deliberately, and a bill that is small enough that saving money is not the argument.

Replacing Linear and Slack

Issues in one place, everything anyone said about those issues in the other, and nothing written down.

Replacing Trello and Slack

A board that everyone can read and nobody maintains, plus a channel where the real assignments happen.

Replacing Asana and Slack

Rules that fire into Slack, replies that never come back, and a portfolio view built for people who do not do the work.

Replacing Confluence and Jira

An Atlassian estate has administrators, permission schemes and an auditor, and none of those are content problems.

Replacing Notion, Linear and Slack

The default startup stack, three subscriptions, and a decision that has to be written down three times to stay true.

Replacing Notion, Jira and Slack

Two tools you can connect this afternoon and one that is a project with a start date and an owner.

Replacing ClickUp and Slack

You already bought one all-in-one product. The Slack subscription next to it is the interesting fact.

Replacing Monday.com and Slack

A board configured by the person who reports on the work, used by the people who have to do it.

Replacing Notion and Trello

A page describing the project and a board describing the same project, kept in step by somebody's memory.

Replacing Airtable and Slack

A relational base doing three jobs at once, and only one of those jobs should move.

Replacing Confluence and Notion

Two subscriptions for writing things down, which almost always means one migration that never got finished.

Replacing Jira, Confluence and Slack

An Atlassian estate with a chat tool bolted to it, and exactly one piece of that you can move this quarter.

Replacing Linear, Notion and GitHub

Three tools a technical team chose on purpose, and none of them has to move anywhere.

Replacing Asana and Notion

A project brief in the tracker, a project page in the doc tool, and a client who has read one of them.

The numbers behind the plans

Stack cost by team size, the pricing-model argument, and what an AI worker actually costs to run.

What your work stack actually costs

Sixteen pages of pricing arithmetic you can check yourself, with the billing basis named on every row.

Tool stack cost for a 10-person team

The size where the free tiers run out on all three products at roughly the same time.

Tool stack cost for a 25-person team

The size where paying monthly instead of annually costs $1,650 a year on its own.

Per-seat pricing and usage pricing charge for different things

One model prices access. The other prices output. Almost every argument about software cost is really about which of those you are buying.

What an AI worker costs, and how the hours are counted

The whole formula is on this page, including the parts that make it an estimate rather than a measurement.

Alternatives to the work tools you pay for by the seat

Sixteen pages about tools teams leave, what leaving actually costs, and when leaving is the wrong call.

Every tool a Polaris worker can be given

One catalog, one credential per tool per organisation, authorized by an owner and used by every worker who carries it.

Questions people ask

+Do I have to move everything at once?

No, and no plan in this cluster recommends it. Every staged migration here starts by pointing new work at Polaris while the old tools stay open in read-only mode. Teams that stall halfway still end up with a working setup rather than a half-broken one.

+Which tools can Polaris read without a migration?

Slack, Notion, Linear and GitHub are in the connection catalog, along with Gmail, Google Calendar, Google Drive, Figma, HubSpot, Stripe, Supabase, WhatsApp, Instagram and open web search. Connections are authorised once for the whole organisation and stored server-side, so AI workers can use them while browsers cannot read the credentials back.

+What happens to years of history in the old tracker?

It stays where it is. Every plan here recommends leaving the incumbent readable rather than trying to reproduce closed tickets from four years ago. Export the archive to CSV for your records, move the work that is still live, and stop paying for seats once nobody needs write access.

+Is Polaris actually free, or does the price arrive later?

The software is free with no seat count and no tier. Unlimited humans, tasks, workstreams and docs are included, and the Chief of Staff is in every organisation from the first sign-in. Billing starts only when an AI worker delivers finished work, at roughly two dollars per human-equivalent hour, itemised on a work log you can challenge line by line.

+How mature is Polaris?

It is in free public beta. There is a working product, a mobile app and four recorded demos including an unstaged machine session, but no customers to point at and no case studies. A migration plan from a beta product deserves more scepticism than one from an established vendor, which is why these pages state their limits in detail.