Spring Clean Your Notion: How to Consolidate Multiple Task Databases (Without Breaking Everything)

Hola amigas! Spring is here, which means it's officially "open every closet and ask why you own 12 identical black t-shirts" season.

And if you're a Notion user? Spring cleaning usually looks like this:

You open your workspace… and realize you somehow have three different "Tasks" databases, two "To-Do" tables, and a random "Admin Tasks (NEW)" list that you forgot existed.

If that's you, you're not messy — you're growing. But multiple task databases will eventually cost you time, create duplicate work, and break your dashboards and automations.

This post walks you through a simple, low-drama way to consolidate multiple task databases into one "source of truth" — without losing data, statuses, or your sanity.

---

The goal before getting started

You're not trying to delete tasks.

You're trying to create one reliable home base where:

• Your databases pull in correctly on your main dashboard
• Your team (or future you) knows where tasks live
• Automations work consistently
• You stop doing "task scavenger hunts"

---

Step 1 — Pick your ONE "source of truth" Tasks database

Before you migrate anything, decide which database is the one you'll keep long-term.

Pick the Tasks database that's most aligned with how you work today:

• It's connected to your main dashboards
• It has the cleanest structure
• It matches your current workflow (statuses, priorities, assignments)

Everything else becomes a temporary "migration source."

Not sure which one to keep? Go with the one your dashboards already reference. Repointing views is easier than migrating all your data twice.

Click on the icon of the databases if it's a linked view, and check the source of the database.

---

Step 2 — Audit your properties before moving a single task

Now it’s time to open both your MAIN database and your OLD database side by side.

Don’t skip this step — it helps make sure you don’t accidentally lose important task details like priority, status, due dates, tags, or notes during the cleanup process.

Open your databases side-by-side and list the properties you actually use, like:

• Status
• Priority
• Due Date
• Assignee
• Project
• Client
• Tags / Category

Then identify the "same thing, different name" properties:

• "Due" vs "Due Date"
• "Owner" vs "Assignee"
• "Type" vs "Category"

Quick note: also check property types (select vs multi-select vs text). A matching name won't help if the type is different.

---

Step 3 — Standardize the MAIN database first

In the database you're keeping, create any missing properties so it can receive tasks without losing important info.

This is also your best moment to clean things up:

• Choose consistent property names
• Simplify status options
• Standardize select/multi-select values

If you're thinking "I'll clean it up later"… come back and finish later so it doesn't get skipped over!

---

Step 4 — Match the OLD databases to the MAIN database

Now go into each old tasks database and rename properties to match the exact property names in your main database.

Why this matters: when you move tasks between databases, Notion maps properties best when names and types match.

This step is the difference between "everything transferred cleanly" and "why is all my Priority data gone?"

Do this in the old database, not the main one. You want your source of truth to stay clean throughout the process.

---

Step 5 — Move tasks in small batches and verify

Do a test batch first — 1 to 3 tasks is perfect.

After moving them, check:

• Did Status map correctly?
• Did select/multi-select values carry over?
• Did people + dates transfer correctly?
• Did relations (Projects/Clients) connect the way you expected?

Once the test batch looks good, move the rest.

---

Step 6 — Lock it in + clean up

Once everything is moved:

• Update dashboards/views to point to the main Tasks database
• Archive old databases (don't delete immediately — give yourself a safety window)

Then update any automations connected to the old database — Zapier/Make flows, buttons, templates, recurring tasks, embeds, and linked views — so they all point to the new "source of truth." I suggest creating a page so you can easily reference what automations you do have.

---

Here's some common mistakes to watch out for:

• Moving tasks before auditing properties
• Renaming properties after migration
• Deleting the old database immediately
• Forgetting to update automations and buttons

---

A quick spring cleaning checklist

• Choose your source-of-truth Tasks database
• List critical properties across all task databases
• Standardize property names + types in your main database
• Rename properties in old databases to match
• Move a small test batch and verify
• Move the full set
• Update dashboards + automations
• Archive old databases after a safety window

---

Final note

If you want this to be painless: 80% of a good consolidation is property prep. The moving part is the easy part.

If you're in spring cleaning mode, come hang out on Sip and Bloom — I share simple Notion systems + strategy you can actually stick with:

→ Read more on Sip and Bloom

And if your workspace has "good bones" but feels unreliable, I offer a full Notion workspace audit + prioritized fix roadmap.

→ Start with the Blossom Assessment

---

About Me & How Biz Strtga Can Help

Hola — I am Jen, the Biz Strtga (strat·e·gista)! I help small business owners and freelancers build Notion workspaces that truly support their goals, with a special focus on service providers.

Through my brand Biz Strtga and my blog, Sip and Bloom, I support entrepreneurs and small teams who are ready to turn scattered workflows into a custom Notion ecosystem.

How we can work together

• Blossom Assessment: Get a full Notion audit and a prioritized roadmap. You’ll receive clear next steps in 5 business days, plus credit toward your next service.
• Cultivation Session: Fix one specific Notion challenge in a focused 90-minute working session. You’ll leave with a clearer setup, quick wins, and next steps — without committing to a full build.
• Workspace Nurture: Upgrade one core area of your workspace with a focused two-week tune-up. Best for Tasks, Content, Clients/CRM, Projects/Delivery, or Admin/Ops — when you want implementation done for you.
• Growth Formula: Rebuild and optimize your existing Notion workspace so it feels lighter and easier to run. Best when you want 2–3 core systems standardized and connected.
• Ecosystem Build: Build a custom Notion workspace designed around how you actually run your business. Best when you need a full operating system from scratch that can grow with you.
• Digital Products – The Apothecary: Ready-to-use Notion templates and tools so you can build a professional system without the custom build price tag.

Based in Los Angeles, I am available for Notion workshops, speaking, brand partnerships, and done-for-you builds. If you are ready to build a workspace that actually works for you, reach out and let us design an ecosystem that supports you.