🧹 Lesson 9.2: Migrating In & Keeping It Clean

You've built something worth keeping. Now let's bring your old notes home from other apps — with realistic expectations — and set up the light maintenance habits and honest backups that keep a workspace clean, trustworthy, and truly yours for years.

📚 What You'll Learn

By the end of this lesson, you will be able to:

Import content from Evernote, OneNote, Google Docs/Word, Apple Notes, CSVs, and Trello/Asana
Set realistic expectations about formatting cleanup and plan a phased migration
Build maintenance habits — a weekly review, archive-vs-delete, naming conventions — that prevent sprawl
Understand Notion's data ownership and lock-in honestly, and mitigate it with regular exports
Recover work using Trash and page history, and export your whole workspace for backup

⏱️ Estimated Time: 55 minutes

🎯 Project: Import one real source (a CSV or a document), do a 10-minute cleanup and review pass, and run a full workspace export so you have a real backup you own.

In This Lesson

📦 Migrating In: The Big Picture

If Notion is your new home, the natural urge is to move everything in at once — box up the whole old apartment and dump it in the doorway. Resist that. A move is the perfect moment to declutter: you touch every item and get to ask "do I actually still want this?" The stuff you never open in Evernote will be exactly as unopened in Notion, just cluttering a nicer house.

So the mental model for this whole first half is "move like you're moving house," not "copy the hard drive." Bring what's alive, leave the rest archived where it is, and clean as you unpack.

⚠️ Set expectations now

Importing is genuinely useful, but it is not a perfect one-click clone. Complex formatting, nested tables, special note features, and app-specific gadgets often need cleanup after they land. Expect to tidy — headings that came in as plain text, images that need re-placing, the odd broken table. That's normal, and doing it a little at a time (see phased migration) keeps it from feeling like a slog.

🔌 Import Playbook by Source

Notion imports from the sidebar: Settings & members → (or the ⋯ menu) → Import, or the Import button at the bottom of the left sidebar. Pick your source and follow the prompts. Here's what to expect from the common ones.

Coming from	How	What to expect
Evernote	Built-in Evernote importer (connect your account)	Notes become pages, notebooks become groups. Simple notes come over well; heavy formatting and web-clips may need cleanup.
OneNote / Word	Built-in importer (Microsoft sign-in) / import .docx	Text and headings transfer; complex layouts, freeform pages, and ink notes don't map cleanly — plan to reformat.
Google Docs	Download as Word/HTML, then import the file (or paste)	Good for text; check headings, links, and images. For a single doc, copy-paste is often fastest.
Apple Notes	No direct importer — export/print notes to PDF, or copy-paste	Small libraries: copy-paste per note. Large ones: a middle step (e.g. export to another format) — accept some manual work.
CSV / spreadsheet	Import → CSV → creates a database	⭐ The cleanest import. Each row becomes a page; columns become properties. Great for contacts, book lists, inventories.
Trello / Asana	Built-in Trello importer / export & import for Asana	Boards → databases, cards → pages. Trello imports fairly well; other trackers may come via CSV.
Markdown / HTML	Import → Text & Markdown / HTML	Markdown maps beautifully to Notion blocks — often the tidiest path if your tool can export it.

✅ Pro Tip — CSV is your friend

If a source is list-shaped (contacts, books, expenses, a task backlog), get it into a CSV and import that — Notion turns it straight into a real database with properties, no cleanup needed. Many apps (including spreadsheets and most trackers) can export CSV, making it the universal on-ramp into Notion's best feature.

💡 A note on Notion AI

After a messy import, AI add-on Notion AI can help reformat or summarize pages ("turn this into headings and bullets"). Handy, but it's a paid add-on — for most cleanup, a few minutes of manual tidying is perfectly fine and costs nothing.

🪜 A Phased Migration Strategy

Don't move everything on day one. A phased approach keeps you productive the whole time and stops the "half-moved, using two apps, trusting neither" limbo that derails people.

graph TD A["Phase 1
Start fresh in Notion
new notes go here"] --> B["Phase 2
Bring active projects
+ frequently-used notes"] B --> C["Phase 3
Import archives
on demand, as needed"] C --> D["Phase 4
Retire the old app
keep one export as backup"]

Phase 1 — Live forward. From today, new notes and tasks go into Notion. Don't touch the archive yet. You immediately get value and learn the tool on real work.
Phase 2 — Move what's active. Bring over current projects and the handful of reference notes you open often. This is 80% of your daily value for 20% of the effort.
Phase 3 — Import archives on demand. Old stuff you rarely need? Leave it in the old app and pull individual items across only when you actually reach for them. Most of it you never will.
Phase 4 — Retire & back up. Once you haven't opened the old app in weeks, export it once for safekeeping and close the account. Done — cleanly.

🧠 Mindset

The fantasy of a "perfect clean migration weekend" is where good intentions go to die. You don't need to move everything, and you don't need to move it flawlessly. A workspace that holds your active life and grows from there beats a pristine archive you never visit. Progress over perfection — always.

✨ Keeping It Clean: Maintenance Habits

A workspace is a garden, not a statue. A little regular tending keeps it useful; neglect turns it into the same overwhelming pile you were trying to escape. The good news: the habits are small.

🔁 The weekly review

Once a week (15 minutes, coffee in hand), run the same loop. This is the single habit that separates thriving workspaces from abandoned ones.

graph LR A["📥 Empty the Inbox
sort each item"] --> B["✅ Update task
statuses"] B --> C["🗂️ Archive what's
done or dead"] C --> D["👀 Glance at
the week ahead"] D --> A

🗄️ Archive vs. delete

Two different actions for two different situations:

Archive — it's finished but you might want it later (a completed project, last quarter's notes). Move it out of the way, don't destroy it. Keep an Archive database (a Status of Archived) or a dedicated Archive page/teamspace so live views stay clean while nothing is lost.
Delete — it's genuinely junk (a duplicate, a test page, a dead idea). Send it to Trash. If you're unsure, archive instead — storage is cheap, and second-guessing a deletion is not.

🏷️ Naming conventions & avoiding sprawl

One database per type of thing, not per project. The most common mess is "database sprawl" — a new tasks database for every project. Instead: one Tasks DB, one Notes DB, one Projects DB, connected by relations (Module 3). Filter, don't multiply.
Name consistently. Pick a pattern and stick to it — e.g. projects as "Project — Client — Q3", meeting notes as "2026-01-15 · Team sync." Dated, front-loaded names sort themselves.
Prune views, not just pages. Delete stale filtered views you never open; they quietly add clutter to every database.

✅ Pro Tip

Make a recurring "🔁 Weekly Review" task (or a Notion Calendar event) with a checklist inside it. When the habit lives in the system, the system reminds you to maintain itself. Meta, but it works.

🔐 Ownership, Lock-In & Backups (Honest Talk)

Time for the honest conversation this course promised back in Lesson 1.1. Notion is cloud-first and proprietary: your content lives on Notion's servers in Notion's format, not as plain files on your disk. That's the price of the sync, collaboration, and databases you love — but it means your data isn't as portable as a folder of text files, and you should plan for that with eyes open.

⚠️ What "lock-in" really means here

If you ever wanted to leave Notion, you couldn't just grab a folder — you'd export, and the export won't perfectly reproduce every Notion-specific feature (relations, rollups, complex views). This isn't unique to Notion; it's true of most powerful cloud tools. The mitigation is simple and you control it: export regularly so you always hold a copy in open formats.

💾 How to fully export your workspace

Go to Settings → Workspace settings and choose Export all workspace content. You'll pick a format:

Markdown & CSV — this is the one to keep as a backup. Pages become .md files (readable in any text editor, forever) and databases become .csv files (openable in any spreadsheet). Open formats you truly own.
HTML — preserves more visual formatting; good for a browsable snapshot.
PDF — Paid for exporting an entire workspace to PDF; fine for individual pages on any plan.

You can also export a single page or database from its ⋯ menu → Export. Do a full Markdown+CSV export every so often (quarterly is plenty for most people) and stash it in your regular backups. Now you're never truly locked in.

♻️ Trash, restore & page history

Two safety nets mean a mistake is almost never permanent:

Trash & restore — deleted pages go to Trash (in the sidebar), where you can search and restore them before they're permanently removed. Delete boldly; the net is there.
Page history — every page keeps a version history you can browse and roll back to. On the Free plan this is 7 days; paid plans extend it (Plus/Business/Enterprise offer 30 days and beyond). Accidentally wrecked a page? Open its ⋯ menu → Page history and restore an earlier version.

💡 The reassuring balance

Cloud-first isn't a trap — it's a trade. You get effortless sync, collaboration, and databases; in return you accept that your data lives in Notion's cloud. Handle your side of the deal with an occasional export and you get the best of both: a powerful connected workspace and a copy of everything in formats that will still open in twenty years.

🎯 Project: Import, Tidy & Back Up

Three real moves that make your workspace fuller, cleaner, and safer — all in one sitting.

🏋️ Import one source, tidy, and export a backup

Objective: Bring one real source into Notion, do a focused cleanup pass, and walk away holding a genuine backup you own.

Instructions (about 30 minutes):

(10 min) Import one real source. Easiest wins: export a list from any app (or make a quick spreadsheet) as a CSV and import it — it becomes a database. Or import a single document (a Google Doc downloaded as Word, or a .docx). Use sidebar → Import.
(10 min) Cleanup + review pass. Fix the imported content: set proper headings, add or rename database properties, delete obvious junk, and archive anything already done. Then empty your Inbox and update a few task statuses.
(7 min) Export a backup. Go to Settings → Workspace settings → Export all workspace content, choose Markdown & CSV, and save the download somewhere in your normal backups.
(3 min) Verify. Open the exported .zip: confirm you see .md files for pages and .csv files for databases. That's your ownership insurance, confirmed.

💡 Hint — no old app handy? Fake a clean import

Open a spreadsheet, make three columns (Name, Status, Notes) and a few rows, save as CSV, and import that. You'll see exactly how rows become pages and columns become properties — the same mechanic that makes CSV the best on-ramp for any real list you migrate later.

✅ Project Completion Checklist

You imported one real source (a CSV database or a document)
You did a cleanup pass: headings/properties fixed, junk deleted, done items archived
You emptied your Inbox and updated a few statuses (a mini weekly review)
You ran a full Markdown & CSV workspace export
You opened the export and confirmed real .md and .csv files inside

🎯 Quick Quiz

Question 1: You want a backup of your Notion workspace that you'll still be able to open years from now, even without Notion. Which export format should you choose?

Question 2: Which migration approach does this lesson recommend?

Best Practices for a Clean, Owned Workspace

✅ Do's

Migrate in phases and declutter as you unpack.
Prefer CSV imports for anything list-shaped — cleanest path to a real database.
Run a 15-minute weekly review and archive done work instead of hoarding it.
Export Markdown+CSV periodically so you always hold your own copy.
Delete boldly — Trash and 7-day page history have your back.

❌ Don'ts

Don't expect a flawless one-click clone — plan for a little cleanup.
Don't spawn a new database per project — that's sprawl; use relations and filters.
Don't skip backups just because Notion is reliable — ownership is on you.
Don't let the Inbox grow forever — an unprocessed inbox is a trust-killer.

📓 Learning Journal

Keep a learning journal — the best place is inside your own Notion. After each lesson, take a few minutes to write down:

Key concepts you learned
Techniques that clicked for you
Questions or confusion points to revisit
Ideas you want to try
Your progress and feelings about learning this

✍️ This lesson's prompt: What's still living in an old app that you'd genuinely miss if it vanished — and what's just digital clutter you can happily leave behind? Sketch your phased plan, and set a realistic date for your first workspace export.

📝 Lesson Summary

🎓 Key Takeaways

Notion imports from Evernote, OneNote, Word, Google Docs, Trello, CSV, and more — but expect some formatting cleanup.
CSV imports are the cleanest path: rows become pages, columns become properties, instantly a database.
Migrate in phases — live forward, move active work, pull archives on demand, retire the old app last.
Keep it clean with a weekly review, archive-vs-delete discipline, consistent naming, and no database sprawl.
Notion is cloud-first and proprietary; mitigate lock-in with periodic Markdown+CSV exports, and lean on Trash and page history for recovery.

🎉 What You've Accomplished

Your workspace is no longer just a fresh start — it's absorbing your real history on your terms, and you know exactly how to keep it tidy and how to walk away with your data any time you want. That's a rare and grown-up relationship with a tool: you use its power fully and you hold your own keys. Few Notion users ever get here. You just did.

❓ Common Questions at This Stage

My imported notes look messy — did I do it wrong?

No — that's expected. Importers transfer text and structure well but rarely reproduce complex formatting perfectly. Do a quick cleanup pass (fix headings, re-place images, adjust properties), and for list-shaped data next time reach for a CSV import, which comes in far cleaner.

How often should I export a backup?

For most personal workspaces, a full Markdown & CSV export once a quarter is plenty. If your workspace is mission-critical or team-shared, monthly is safer. Store it wherever your other important files are backed up. The habit matters more than the frequency.

I deleted something important — is it gone forever?

Almost certainly not. Check Trash in the sidebar and restore it. If you didn't delete the page but wrecked its contents, open the page's ⋯ menu → Page history and roll back — you get 7 days of history on the Free plan, longer on paid plans.

🔭 Looking Ahead

You now have everything: the concepts, the blocks, the databases, the views, the automations, and a clean, portable, well-fed workspace. The next lesson is the grand finale — the Capstone, where you design and build your own complete personal operating system and tie the entire course together. Bring everything you've learned. 🎓

✅ Before the Next Lesson

Complete at least one real import and one export this week
Do a full 15-minute weekly review so the habit is warm
Skim your workspace and note what's working and what feels cluttered — you'll use this in the Capstone
Write your Learning Journal entry for this lesson

📚 Additional Resources

🌟 Encouragement for the Journey

Moving in and keeping house aren't the glamorous parts — but they're what turn a shiny new app into a home you'll still love next year. You've packed light, cleaned as you unpacked, and hidden a spare key under the mat. Everything is in place now. Let's go build your operating system. 🧹