The Ultimate Guide: Moving Large Notion Workspaces Between Accounts (Without Export/Import Headaches)

The Problem Everyone Faces (But Nobody Talks About)

You've spent months building your perfect Notion workspace. Hundreds of pages, databases with thousands of entries, embedded files, images, and intricate linked databases that make your workflow seamless. Now you need to move it all to a different Notion account—maybe for work, a new organization, or personal reorganization.

You think: "No problem, I'll just export and import."

Wrong.

You hit the dreaded 5MB import size limit on free plans (or even the 50MB limit on paid plans for really large workspaces). Your carefully crafted workspace is now trapped, fragmented across multiple export files, and the traditional import process either fails or corrupts your data structure.

Sound familiar? You're not alone.

Why Traditional Export/Import Fails

The Hard Limits

Notion's import system has strict file size limitations:

Free Plan: Maximum 5MB per import file
Paid Plans: Maximum 50MB per import file
Large workspaces: Often exceed 100MB-500MB+ with attachments and images

What Breaks During Import

Relation properties between databases get severed
Synced blocks lose their connections
File attachments may fail to transfer
Database views and filters don't always migrate correctly
Page hierarchies can become flattened or disorganized
Permissions and sharing settings are lost Trying to split your export into smaller chunks? That creates even more problems with broken links and references.

The Solution: The Teamspace Transfer Method

This method leverages Notion's native sharing and duplication features to transfer data seamlessly, regardless of size. No export files, no import errors, no broken relationships.

How It Works (The Theory)

Instead of exporting and importing files, you:

Create a teamspace in your source account
Move all your content into that teamspace
Invite your destination account as a member of the teamspace
Access the teamspace from your destination account
Use Notion's "Move to" feature (which triggers duplication when moving between workspaces)
The content gets duplicated to your destination workspace The beauty? Notion handles all the heavy lifting internally, maintaining database relationships, file integrity, and page structure.

Step-by-Step Tutorial: Complete Migration Guide

Prerequisites

Source account: The account with your data (Account A)
Destination account: Where you want the data to go (Account B)
Paid Notion plan on the source account (Teamspaces require Plus, Business, or Enterprise)
30-60 minutes of focused time

Phase 1: Prepare Your Source Account

Open Notion on your source account (Account A)
In your sidebar, scroll to the "Teamspaces" section
Click the "+" button next to "Teamspaces"
Name it something clear: "Migration - [Your Name]" or "Transfer Workspace"
Set the teamspace type:
Click "Create teamspace" Pro Tip: Don't use "Private" teamspaces if you're on a Business plan—they have restrictions on guest access that might complicate things.

Now comes the organization part. You need to move everything you want to transfer into your new teamspace.

Method 1: Drag and Drop (Recommended for organized workspaces)

In your sidebar, locate the pages/databases you want to transfer
Click and hold the page/database icon
Drag it into your "Migration" teamspace
Drop it inside the teamspace
Notion will move the page and all its subpages automatically

Method 2: Using the Move Feature (For scattered content)

Open any page you want to transfer
Click the "•••" menu at the top right
Select "Move to"
Choose your "Migration" teamspace from the list
Click **"Move" ** Important Considerations:

Databases with relations: Move the main database first, then move any related databases to preserve connections
Nested pages: Moving a parent page automatically moves all child pages
Check your work: After moving everything, open your teamspace and verify all content is there

What to Move:

✅ All pages you want to transfer

✅ All databases (move these carefully to preserve relations)

✅ Templates you've created

✅ Any workspace-level resources

What NOT to Move:

❌ Private pages you don't want to share

❌ Test pages or drafts

❌ Anything with sensitive data you don't want temporarily visible to the destination account

Phase 2: Grant Access to Destination Account

This is where the magic happens. You're essentially creating a bridge between the two accounts.

In your source account (Account A), click on your "Migration" teamspace name in the sidebar
Click the "•••" menu next to the teamspace name
Select "Teamspace settings"
Go to the "Members" tab
Click "Add members"
Type the email address associated with your destination account (Account B)
Important: Set their role to "Teamspace member" (not owner)
Click **"Invite" ** What Happens Next:

Account B will receive an email invitation
They can now see and access everything in the teamspace
The data is still owned by Account A, but Account B has full visibility

Switch to your destination account (Account B):

Check the email associated with Account B
Open the invitation email from Notion
Click "Accept invitation"
Or: Open Notion on Account B, you should see a notification to join the teamspace
Click to accept and join Once accepted, the teamspace will appear in Account B's sidebar under "Teamspaces."

Phase 3: Transfer Content to Destination Account

This is where Notion's intelligent duplication system does the heavy lifting.

On your destination account (Account B), go to the sidebar
Find the "Migration" teamspace under the Teamspaces section
You should see all the pages and databases from Account A
Browse through to verify everything is visible and accessible Here's the critical part: When you try to move content from a teamspace to your private workspace across different accounts, Notion duplicates the content instead of moving it.

This is exactly what we want.

For Individual Pages:

Open any page in the shared teamspace
Click the "•••" menu at the top right
Select "Move to"
Choose "Private" (or wherever you want it in your Account B workspace)
Click **"Move" ** What actually happens: Notion will show a message saying something like "This page will be duplicated" because you don't have permission to move it out of the teamspace. This is expected behavior and exactly what we want.

For Databases:

Important: Move the main database first
Open the database page
Click "•••" menu → "Move to"
Select your destination location in Account B
Click "Move" (it will duplicate)
Then move any related databases to preserve relationships

For Multiple Pages at Once:

Notion doesn't support bulk moving from teamspaces in the traditional sense, but you can:

Create a new parent page in your destination workspace
One by one, move subpages into that parent page
Or: Select multiple pages in the teamspace, but you'll need to move them individually

Pro Tips for Large Migrations:

Move in batches: If you have hundreds of pages, do it in groups of 20-30 to avoid rate limiting
Start with templates: Move template pages first so you can test the process
Database order matters: Move parent databases before child databases to preserve relations
Check relations: After moving databases, verify that relation properties still work

Phase 4: Verify and Clean Up

This is crucial—don't skip it.

Checklist:

✅ Page count: Does Account B have the same number of pages as you moved?

✅ Database relationships: Open databases and check that relations still connect properly

✅ Files and images: Verify that all embedded files and images loaded correctly

✅ Linked databases: If you use linked database views, confirm they still work

✅ Formulas: Check that database formulas calculate correctly

✅ Subpages: Ensure the hierarchy structure is intact

✅ Templates: Test your template pages to ensure they function

How to Check Database Relations:

Open a database with relation properties
Click on a relation field
Verify it shows the correct linked database
Create a test entry to ensure the relation works

If Something Broke:

Broken relations: You may need to re-link databases manually in Account B
Missing files: Check if files exceed size limits; you may need to re-upload
Corrupted pages: Go back to the teamspace and re-move that specific page

Now that everything is in Account B, organize it how you want:

Move pages from Private to appropriate locations
Create new teamspaces in Account B if needed
Set up your sidebar organization
Adjust permissions if Account B is a shared workspace Once you're 100% confident everything transferred correctly:

On Account B (Destination):

Go to the "Migration" teamspace
Click "•••" menu next to the teamspace name
Select "Leave teamspace" On Account A (Source):
Go to teamspace settings
Remove Account B as a member
Optional: Archive or delete the migration teamspace
Optional: Delete the original pages if you no longer need them in Account A ⚠️ Warning: Don't delete anything from Account A until you've verified for at least 24-48 hours that everything works in Account B.

Troubleshooting Common Issues

Issue 1: "You don't have permission to move this page"

Cause: You're trying to move a page from a teamspace where you're only a member (not owner).

Solution: This is actually correct behavior. The page will be duplicated instead of moved, which is what we want. Click "Move" anyway—Notion will handle the duplication.

Issue 2: Database Relations Are Broken

Cause: The related database wasn't moved, or was moved after the main database.

Solution:

Move all related databases to Account B
In Account B, open the database with the broken relation
Edit the relation property
Re-link it to the correct database in Account B

Issue 3: "Rate Limit Reached" Error

Cause: You're trying to duplicate too much content too quickly. Notion limits duplication to 50,000 blocks per hour.

Solution:

Wait one hour
Continue moving content in smaller batches
Consider moving your workspace in phases over several hours

Issue 4: Files or Images Won't Load

Cause: Files may exceed Account B's upload limits, or there's a connectivity issue.

Solution:

Check Account B's plan limits (Free: 5MB per file, Paid: 5GB per file)
For large files, re-upload them manually to Account B
Check your internet connection and try again

Issue 5: Teamspace Doesn't Appear in Account B

Cause: Invitation wasn't accepted, or Account B doesn't have permission.

Solution:

Check Account B's email for the invitation
Resend the invitation from Account A
Ensure Account A's teamspace is set to "Closed" not "Private"
Verify Account B's email address is correct

When to Use This Method vs. Traditional Export/Import

Use the Teamspace Method When:

✅ Your workspace is larger than 5MB (free) or 50MB (paid)

✅ You have complex database relationships you need to preserve

✅ You want to maintain page structure and hierarchy

✅ You have linked databases or synced blocks

✅ You're moving an active workspace that's constantly updated

✅ You have source account access (you own or admin both accounts)

Use Traditional Export/Import When:

✅ Your workspace is small (under 5MB)

✅ You're doing a one-time backup

✅ You want a local copy of your data

✅ You're switching platforms (leaving Notion entirely)

✅ You don't have a paid plan on the source account

Pro Tips for Power Users

Tip 1: Pre-organize Before Moving

Before starting the migration:

Create a clear hierarchy in your source workspace
Group related content under parent pages
This makes the transfer cleaner and easier to manage

Tip 2: Use a Staging Teamspace

If you're migrating a massive workspace:

Create multiple teamspaces (e.g., "Migration - Databases", "Migration - Content")
Move content in logical groups
Transfer each group separately
This prevents overwhelming both accounts and makes troubleshooting easier

Tip 3: Document Your Database Structure

Before moving:

Take screenshots of your database schemas
Note all relation properties and what they connect to
Export a CSV of database contents as backup
This documentation is invaluable if you need to rebuild relations

Tip 4: Leverage Duplication for Multi-Account Workflows

This method isn't just for one-time migrations. You can use it for:

Syncing content between work and personal accounts
Sharing templates with clients
Creating backups in a secondary account
Testing changes in a safe environment before implementing in your main workspace

Tip 5: Coordinate Timing for Team Migrations

If you're migrating a team workspace:

Schedule downtime: Let your team know when the migration will happen
Freeze edits: Ask team members not to make changes during migration
Assign roles: Have specific people verify different parts of the workspace
Staggered access: Add team members to the new workspace in phases

Advanced Scenarios

Scenario 1: Migrating with Active Collaborators

If your workspace has multiple active users:

Create a transition period: Keep both accounts active for 1-2 weeks
Announce the migration: Let collaborators know about the new workspace
Redirect gradually: Move teams one at a time
Update bookmarks: Remind people to update their Notion bookmarks

Scenario 2: Partial Workspace Migration

Only moving some content?

Create a temporary teamspace just for migration content
Move only specific pages/databases to the teamspace
Transfer to destination account
Delete the temporary teamspace once complete

Scenario 3: Multi-Account Consolidation

Consolidating 3+ Notion accounts into one:

Use the same destination account for all migrations
Create separate migration teamspaces for each source account
Transfer content in parallel (you can do multiple at once)
Merge and reorganize in the destination account afterward

Frequently Asked Questions

Q: Will this work with the free plan?

A: Partially. You need a paid plan on the source account to create teamspaces. However, the destination account can be on the free plan. If both accounts are free, you'll have to use traditional export/import.

Q: How long does the migration take?

A: It depends on workspace size:

Small workspace (50-100 pages): 30 minutes - 1 hour
Medium workspace (100-500 pages): 2-4 hours
Large workspace (500+ pages, multiple databases): 4-8 hours or more The actual moving is fast, but verification and organization take time.

Q: Will my page history transfer?

A: No. When content is duplicated, you lose the version history. Only the current version transfers. If you need history, you'll need to keep the source account accessible.

Q: Can I automate this process?

A: Not easily. Notion's API doesn't fully support cross-workspace duplication. This manual method is currently the most reliable for large migrations.

Q: What about Notion AI content?

A: AI-generated content within pages will transfer as regular text. However, AI access is tied to the workspace subscription, so you'll need AI enabled on the destination account to generate new AI content.

Q: Will formulas and rollups still work?

A: Yes, as long as all related databases are moved together. Formulas are preserved, but you may need to verify they're calculating correctly after migration.

Real-World Success Stories

Case Study 1: Freelancer to Agency

Challenge: Solo freelancer scaling to a 5-person agency needed to migrate 800+ pages and 15 client databases from personal account to business account.

Solution:

Created 3 separate teamspaces: Clients, Internal, Templates
Moved content over 2 days
Added team members gradually
Result: Zero data loss, all relations preserved

Case Study 2: University Research Lab

Challenge: Graduate student graduating needed to transfer 4 years of research notes (2,500+ pages) to the lab's permanent account.

Solution:

Used teamspace method over winter break
Organized content into topic-based hierarchies first
Transferred in batches of 200 pages
Result: Complete transfer with full citation database intact

Conclusion: Take Control of Your Notion Data

The 5MB import limit is frustrating, but it doesn't have to be a barrier. The teamspace transfer method is reliable, preserves data integrity, and works for workspaces of any size.

Yes, it takes more time than a simple export/import. But the peace of mind knowing your databases, relations, and page structures remain intact is worth it.

Key Takeaways

✅ Teamspace method bypasses file size limits entirely

✅ Database relationships and page hierarchies are preserved

✅ Content is duplicated, not moved, creating a clean separation

✅ Works for workspaces of any size

✅ Requires a paid plan on source account

✅ Takes time but is highly reliable

Your Next Steps

Backup your source workspace (export as a safety measure)
Create your migration teamspace
Move content in organized batches
Invite destination account
Transfer and verify everything works
Clean up and celebrate your successful migration! 🎉

Additional Resources

Notion's Official Guide to Teamspaces
Understanding Notion's Sharing & Permissions
Notion Import Data Documentation
Notion Community Forum - for troubleshooting specific issues

Have you successfully migrated a large Notion workspace using this method? Share your experience and tips in the comments below!

Last updated: February 2026