Move from Notion to Atlas.
To move from Notion to Atlas, export your workspace as Markdown and CSV from Notion Settings, then bring them into Atlas. Page content goes into Atlas docs as Markdown, and database CSVs can become Atlas tasks or CRM records. Text, headings, and tables carry over. Notion-specific view configurations, synced blocks, and comment threads do not, and this guide is honest about each one.
Export your data from Notion.
Notion exports Markdown, CSV, HTML, and PDF from its own Settings. You do this inside Notion, before you touch Atlas. Owners and members can export their own content; a full workspace export is an owner action.
- Open workspace settings. In Notion, click
Settingsin the left sidebar, then open theSettingstab for your workspace. Scroll to theExport contentsection. To export a single page instead, open the page, click the•••menu at the top right, and chooseExport. - Choose Markdown and CSV as the format. Notion offers Markdown and CSV, HTML, and PDF. Pick Markdown and CSV. Pages come out as
.mdfiles that keep headings, lists, and tables, and every database comes out as a.csvfile, which is the format Atlas reads for structured records. - Include subpages and databases. Turn on
Include subpagesso nested pages come with their parents, and setInclude databasesto the current view or every view depending on how much you want. Choose to include files and media if you want attachments in the archive rather than as links. - Start the export and wait for the email. Click
Export. Notion assembles a.ziparchive in the background and emails you a download link when it is ready. Large workspaces can take several minutes. The link is time limited, so download it promptly. - Unzip and check the archive. Extract the
.zip. You will see a folder tree of Markdown files mirroring your page hierarchy, a.csvfor each database, and a media folder if you included files. Open a couple of files to confirm the content looks right before you import anything.
Note on PDF export: Notion gates PDF export of an entire workspace behind its paid plans, and PDF is not a good import format anyway. Markdown and CSV is the right choice for a migration because it preserves structure a machine can read.
What carries over, and what does not.
A migration guide that pretends everything transfers perfectly is lying to you. Here is the real split, so you can decide what to rebuild by hand.
Carries over cleanly
- Page content. Headings, paragraphs, bullet and numbered lists, quotes, code blocks, and simple tables survive the Markdown export intact.
- Database rows and fields. Every database becomes a CSV with your columns as headers. Text, numbers, dates, checkboxes, and single and multi select values all come through as data.
- File attachments. If you include files in the export, images and uploaded documents come along in the archive, and you attach them in Atlas by hand.
- Page hierarchy, as a map. The folder structure of the Markdown export mirrors your nesting, so you have a map to rebuild the same structure in Atlas.
Does not carry over, and must be rebuilt
- View configurations. Notion board, calendar, gallery, and timeline layouts are not in the export. The underlying data is; the saved views are not. You recreate the views you want in Atlas, which takes minutes because the data is already there.
- Synced blocks and linked databases. These are Notion constructs. A synced block exports as a static copy, and a linked database view is not represented at all.
- Comments and page history. Comment threads and the edit history do not export. If a decision lives only in a comment, copy it into the page body before you export.
- Formulas and rollups. A Notion formula exports its computed value at export time, not the formula. Rollups export as static values too. You rebuild the logic in Atlas.
- Relations between databases. Cross-database relations export as text references, not live links. You reconnect the important ones in Atlas after the import.
Import into Atlas.
Atlas reads Markdown and CSV directly. The point of the move is not a like for like copy of Notion. It is that your docs, tasks, projects, and CRM now sit on one graph with an assistant that can act on them.
Atlas docs are written in Markdown, so paste the content of each exported page into a new Atlas page and its headings, lists, and tables come with it. Rebuild the page tree as you go. For a task database, open Settings, then Data, and import the CSV into a project; the importer reads columns named title, description, status, priority, dueOn, and startsOn, so rename your columns to match. For a contacts or companies database, use the import in Atlas CRM, which suggests a column mapping and previews the rows before it creates records.
Once the data lands, you get what Notion could not give you: the same records feed Tasks, CRM, and Docs at once, and Ask Atlas can read all of it and take the next step. Ask it to turn an imported project database into a live board, assign owners, and flag anything overdue, and it does the work rather than describing it.
It is free to start while you check the import, then invite the rest of the team once it looks right. The whole Atlas product is described on the Atlas overview.
Notion and Atlas, compared.
Notion is a strong document and database tool with an enormous template ecosystem. Atlas is a wider operating surface with an assistant that acts. Both statements are true. Pick the one that fits the job.
| Capability | Notion | Atlas |
|---|---|---|
| Freeform docs and wikis | Excellent, its core strength | Good, structured docs that link to work |
| Databases and templates | Very deep, huge template library | Structured objects across 16 modules |
| Native CRM and pipeline | Built by hand from a database | Purpose-built CRM that updates from activity |
| Contracts and e-signature | Not built in | Draft, redline, and sign in the workspace |
| PDF editing tools | Not built in | 39 PDF tools inside the tenant |
| Assistant that takes action | AI writes and summarizes | Reads your data, then creates and moves records |
| Single sign-on | SAML on business and enterprise plans | SAML single sign-on on paid plans |
| Security certifications | Holds independent audits | None held today, stated plainly on the trust page |
| Entry price | Free personal, paid per member | Free to start |
Pricing and plan details change. Check the pricing page for the current Atlas numbers, and Notion's own site for theirs.
Migration questions.
The things people ask before they move a team off Notion.
Will my Notion databases become tasks or just tables in Atlas?
You choose by where you import it. Each Notion database is a CSV. A task or project tracker goes in through the task import, into the Atlas project you pick. A contacts or companies database goes in through the CRM import, which lets you map columns and preview rows before anything is created. Other databases are best kept as tables inside an Atlas doc.
Do Notion formulas and rollups survive the export?
No. Notion exports the computed value at the moment of export, not the formula or the rollup logic. The numbers come across as static data. You rebuild the calculations you still need inside Atlas, which most teams find is fewer than they expected.
Can I move just one workspace or one team first?
Yes, and it is the sensible way to do it. Export a single space or a set of pages, import them into a free Atlas workspace, and check the result before you move the rest of the company. Nothing forces an all at once cutover.
What happens to comments and page history?
They do not export from Notion and cannot be recovered by Atlas. If a decision or a piece of context lives only in a comment thread, paste it into the page body before you export so it travels with the content.
Does Atlas have the security certifications Notion has?
No. Atlas holds no security certifications today, and the trust page says so in full. If your migration is blocked by a procurement requirement for an audited vendor, Notion or another certified tool is the right answer, and we will not pretend otherwise.
Who should not migrate.
Atlas is not the right move for everyone leaving Notion. If you are one of these, stay where you are for now.
Do not migrate if
- Your procurement requires an audited vendor. Atlas holds no certifications yet. A team that must show a SOC 2 report to close the review should not move.
- Notion is mainly a public wiki or knowledge base for you. Notion's published sites and template gallery are genuinely strong. If that is your whole use, Atlas is a wider tool than you need.
- You depend on a large library of Notion community templates. Those do not transfer, and rebuilding a heavily templated system by hand is real work.
- You want a document tool, not an operating system. Atlas earns its keep when it replaces several tools at once. If you only want docs and databases, that is Notion's home turf.
Migrating from a different tool? Read the guides for ClickUp, Asana, and HubSpot.
Bring Notion into one graph.
Export from Notion, import into Atlas, and put your docs, tasks, and pipeline on a single work graph with an assistant that acts. It is free to start, so you can test the whole import before you commit.