Crewtool
Directory — Est. 2025
Crewtool·Guides
GUIDE

Migrating from Notion to Dooray!

Practical guide for teams that must move from Notion to Dooray! due to Korean public/finance security requirements.

Market: KoreaAudience: Small team

When this migration is needed

  • Public/finance deals require in-country data residency
  • Notion fails security review (no on-prem option)
  • Need Korean approval workflow
  • Cost optimization (leverage Dooray free tier)

Prep (1 week)

1. Back up all Notion pages/DBs (Workspace Settings → Export) 2. Create Dooray account + design project/wiki structure 3. Set migration priority: wiki → projects → tasks

The actual move (2–4 weeks)

Docs / wiki Export Notion pages (HTML/Markdown) → manually copy into Dooray Wiki. Block structures don't map perfectly — reorganize after copy.

Databases / tasks Notion DB → CSV export → manual import to Dooray projects/issues. Field mapping requires thought.

Link cleanup Replace internal links one by one with new URLs. Hard to automate.

Post-migration (1-month overlap)

1. Run Notion and Dooray in parallel for a month 2. New work in Dooray, old references in Notion 3. Gather team feedback, then cancel Notion

Common pitfalls

  • Trying for perfect block style replication: impossible. Reorganize
  • Canceling Notion first: permanent data loss risk
  • Not designing approval flow in advance: misses Dooray's strength

Typically 1–2 months for teams under 20.

Featured in this guide
FAQ

Do I abandon Notion entirely?

Keep public wikis/content; move only internal confidential docs to Dooray. Parallel ops is also valid.

Any migration automation tools?

No full automation. You can connect Notion API + Dooray API yourself, but manual cleanup is required due to block-structure differences.

Productivity hit during migration?

1–2 weeks of temporary 20–30% drop. Recovers once the team settles into Dooray.