# How long does it take to migrate off Confluence Data Center?

> A manual Confluence Data Center migration runs weeks once you add content review, permissions, macros, broken links, and rollout, and the condition of your knowledge base drives the timeline more than headcount does. This guide breaks down each phase, what stretches it, and how the import itself can finish in a day.

- Date: 2026-08-12
- Tags: confluence, confluence-alternatives, migration, documentation, on-prem

---
A manual Confluence migration can take weeks once you include content review, permissions, macros, broken links, and rollout.
The exact timeline depends more on the condition of your knowledge base than team size.
With Falconer, the initial import and setup can be completed within a day.

Most of that time goes into deciding what to keep, rebuilding content that does not export correctly, validating permissions, and helping teams adopt the new system.
Tools like Falconer handle the technical migration for you: connect Confluence, choose your spaces, and let Falconer import the content without changing the original instance.

Confluence Data Center is Atlassian's self-managed, on-premise version of Confluence, the wiki many engineering organizations run behind their own firewall.
It reaches [end of life on March 28, 2029](https://community.atlassian.com/forums/Data-Center-articles/Reminder-Upcoming-changes-to-Data-Center-products/ba-p/3210679), when licenses expire and the product becomes read-only, so most teams reading this are working against a fixed deadline.

### TLDR

- Importing Confluence takes hours to a day. Reviewing the content, checking permissions, and switching teams to the new system take weeks.
- A 50 to 200-person engineering organization should budget six to eight weeks for essential documentation and another four to six weeks for everything else.
- Stale content is the biggest source of delay.
- Macros, Marketplace apps, permissions, and broken links can add more time.
- Falconer is the fastest, most complete option: connect Confluence, choose your spaces, and let Falconer handle the import.
- Falconer preserves your page hierarchy, leaves the original instance unchanged, and makes imported content searchable alongside code, Slack, Linear, and other sources.
- Confluence Data Center becomes read-only on March 28, 2029. New purchases, expansions, upgrades, and Marketplace app sales end on March 30, 2028, but existing customers can keep renewing their current footprint until the 2029 expiry.

![Side-by-side comparison of a manual Confluence migration taking 10 to 14 plus weeks against a Falconer migration taking hours to one day](/images/guides/confluence-data-center-migration-timeline-comparison.webp)

## Why do two migrations take such different amounts of time?

Two teams can have the same number of pages and completely different timelines.

A clean instance with current content and simple page trees moves quickly.
An older instance with custom macros, restricted spaces, duplicate pages, and years of abandoned content becomes a cleanup project before it becomes a migration.

The timeline depends on five questions:

1. How much content do you have?
2. How much of it is still useful?
3. How heavily do pages use macros and Marketplace apps?
4. Do permissions need to map exactly?
5. Are you copying the old hierarchy or designing a better one?

The last question matters most.
Copying everything as-is looks faster, but it brings stale pages, broken links, duplicates, and poor organization into the new platform.
That creates more work later.

## How long does each phase take?

![Typical migration timeline across five phases - import, review, essential docs, remaining docs, and maintenance - totaling 10 to 14 plus weeks](/images/guides/confluence-data-center-migration-timeline-phases.webp)

A typical migration for a mid-size engineering organization looks like this:

| Phase | Typical duration (50-200 engineers) | What happens | Risk if rushed |
| --- | --- | --- | --- |
| Import | Hours to 1 day | Connect spaces and make content searchable | Assuming the migration is finished |
| Review | 1-2 weeks | Decide what to keep, archive, or delete | Moving stale or conflicting pages |
| Essential docs | 6-8 weeks | Move daily-use docs, assign owners, check permissions, fix links | Breaking critical docs or exposing restricted content |
| Remaining docs | 4-6 weeks | Move secondary and rarely used content | Delaying the switch for pages nobody reads |
| Maintenance | Ongoing | Keep pages accurate and assign responsibility | Letting the new system become outdated |

### Hours to one day: import the content

The extraction or import is usually the shortest phase.

Confluence can [export spaces as XML, HTML, or PDF](https://confluence.atlassian.com/doc/export-content-to-word-pdf-html-and-xml-139475.html).
XML retains the most structure and metadata.
HTML is more portable.
PDF is useful for reading, not migration.
Macros and dynamic content often need separate handling.

Falconer handles this step for you through a [read-only Confluence integration](https://falconer.com/about/integrations/confluence/).
Connect Confluence, choose the spaces you want, and Falconer imports them while preserving the page hierarchy.
The content becomes searchable alongside code, Slack, Linear, and other sources, while your original Confluence instance stays unchanged.

That gives you a fast, low-risk migration without export scripts, manual copying, or a disruptive switch.

### One to two weeks: review the content

Next, place each page into one of three groups.

| Bucket | Definition | Example | Action |
| --- | --- | --- | --- |
| Keep | Current, trusted, actively used | A deployment runbook updated this quarter | Migrate first, assign an owner |
| Archive | Historically useful, no longer operational | A 2021 postmortem for a retired service | Keep accessible read-only, do not migrate |
| Delete | Duplicated, obsolete, or ownerless | Three conflicting onboarding pages | Cut before it pollutes the new system |

Falconer also handles much of the work after import.
Once you [migrate your Confluence docs](https://falconer.com/docs/set-up/connect-sources/), it can identify outdated pages, duplicate content, and missing documentation.
Your team reviews the recommendations instead of inspecting every page manually.

### Six to eight weeks: move essential docs

Start with the documentation people use every day: deployment guides, runbooks, architecture docs, API references, onboarding material, current product docs, and active policies.

For a 50 to 200-person engineering organization, moving these pages typically takes six to eight weeks.
Teams must assign owners, check accuracy, fix links, match permissions, and confirm that people can find what they need.

Keep both systems available during this period.
Use Confluence as a reference while teams begin using the new system.

### Four to six more weeks: move remaining content

Secondary runbooks, internal processes, older postmortems, meeting notes, and rarely used documentation can follow after the essential content.
This work often adds another four to six weeks.

Not everything needs to move.
Keep the old instance available in read-only mode and migrate the remaining pages only when people still need them.

### After the switch: keep docs accurate

The migration is not finished until someone is responsible for keeping the new documentation accurate.

Falconer keeps working after the migration.
It connects documentation to code and other sources, proposes updates when they change, and identifies missing or duplicate pages.
Unlike a static wiki, [Falconer keeps imported Confluence docs current](https://falconer.com/guides/falconer-vs-confluence/) instead of leaving your team to maintain them by hand.

## How to migrate off Confluence fast

A Falconer migration takes **hours to one day**, compared with weeks for a manual migration.
Falconer handles the import, preserves your structure, and makes the content searchable.
Your team only chooses which spaces to bring over and reviews Falconer's recommendations.

| Step | What happens | Typical time |
| --- | --- | --- |
| Connect Confluence | Authorize Falconer through a read-only connection | Minutes |
| Choose spaces | Select the spaces you want to migrate | Minutes |
| Import content | Falconer imports pages and preserves their hierarchy | Hours |
| Review results | Falconer identifies outdated pages, duplicates, and missing docs | Same day |
| Start using Falconer | Content is searchable alongside code, Slack, Linear, and other sources | Within one day |
| Keep docs current | Falconer proposes updates when connected sources change | Ongoing |

The original Confluence instance stays unchanged.
There are no export scripts, manual copying, or blank-slate setup.
Teams can start using Falconer immediately and retire Confluence when they are ready.

### The Falconer migration process

1. Connect Confluence through the [read-only integration](https://falconer.com/about/integrations/confluence/).
2. Choose the spaces you want to migrate.
3. Let Falconer import the content and preserve the page hierarchy.
4. Review outdated, duplicate, and missing content identified by Falconer.
5. Use the imported content immediately while Falconer keeps it current.

Falconer turns migration from a multi-week transfer project into a same-day setup.
The remaining work is review, not moving files.

## How long does a migration take by organization size?

The six-to-eight-week estimate applies to organizations with 50 to 200 engineers.
The estimates below are starting points, not guarantees.
The amount and quality of your content matter more than headcount.

| Organization size | Import | Essential docs | Remaining docs | Estimated total |
| --- | --- | --- | --- | --- |
| Under 50 engineers | Hours to 1 day | 3-5 weeks | 2-4 weeks | About 5-9 weeks |
| 50-200 engineers | Hours to 1 day | 6-8 weeks | 4-6 weeks | About 10-14 weeks |
| 200+ engineers | 1-2 days | 8-12+ weeks | 6-10+ weeks | 14+ weeks, usually one team at a time |

Large organizations usually move one team at a time.
This takes longer overall but reduces disruption for each team.

## What delays a Confluence migration?

Five things stretch the timeline more than page count does.

| Cause | Why it adds time | Possible delay |
| --- | --- | --- |
| Pages with many macros | Macros and Marketplace apps may not work outside Confluence | Days to weeks |
| Complex permissions | Space and page access rules may not match the new system | Days for review and testing |
| Attachments and internal links | Files may need new links, and old page URLs may break | Work continues throughout the migration |
| Large amounts of stale content | Every extra page must be reviewed | Weeks |
| A new folder structure | Teams must agree on how to organize the content | 1-2+ weeks before moving content |

### Macros and Marketplace apps

Macros are page elements such as Jira issue lists, table filters, and content pulled from other pages.
They may not work after an export, leaving parts of a page missing.
Atlassian documents which [content and apps migrate](https://support.atlassian.com/migration/docs/what-migrates-with-the-confluence-cloud-migration-assistant/) and recommends that teams [review Marketplace apps before moving](https://support.atlassian.com/migration/docs/assess-apps-with-the-confluence-cloud-migration-assistant/).
It also lists [apps with a Cloud migration option](https://confluence.atlassian.com/kb/marketplace-apps-for-confluence-that-are-available-in-cloud-with-migration-paths-1069029108.html).
Find pages that rely on macros early because they may need to be rebuilt.

### Complex permissions

Confluence [space permissions](https://confluence.atlassian.com/doc/space-permissions-overview-139521.html) and [page restrictions](https://confluence.atlassian.com/doc/page-restrictions-139414.html) may not match the access controls in a new platform.
Check restricted pages before giving people access.
Otherwise, a page that was private in Confluence could become visible to the whole company.
Atlassian explains the existing rules in its guide to [Confluence Data Center permissions](https://support.atlassian.com/confluence/kb/understanding-permission-in-confluence/).

### Attachments and internal links

Attachments may need relinking, and internal URLs can break when page paths change.
Large tables, callouts, inline comments, checklist formatting, and Confluence-specific images may also need validation after import.
Atlassian maintains a [troubleshooting guide](https://support.atlassian.com/migration/docs/troubleshoot-migration-with-confluence-migration-assistant/) for the errors that show up here.

### Too much stale content

Migrating every page feels safer, but it creates more validation work and makes the destination harder to trust.
The fastest successful migrations move current knowledge first and leave uncertain content accessible in the old system until someone proves it still matters.

### Rebuilding the hierarchy

A decade-old Confluence tree usually reflects the teams and projects of years past, not the organization today.
Redesigning it takes longer than copying it, and it prevents the new platform from reproducing the same navigation problems on day one.

## Does the destination change the timeline?

Yes.
Your destination determines how much content transfers correctly and how much you must rebuild.

Confluence Cloud preserves more of Confluence's structure and apps, but it also carries over stale content.
Other documentation platforms may require exports, conversion, and manual rebuilding.
Falconer is designed to handle the move for you: it imports selected spaces through a read-only connection, preserves their hierarchy, makes the content searchable, and helps you clean up what came over.
That makes it the quickest path to a complete migration without simply copying the old problems.

## How can you shorten a Confluence migration?

1. Choose the new platform first. It determines which export format to use and what must be rebuilt.
2. Import before cleaning. Review the content in the new system instead of cleaning every page in Confluence first.
3. Start with one team. Check permissions, formatting, and daily use before adding more teams.
4. Move frequently used content first. Do not delay the switch for abandoned pages.
5. Keep Confluence available as read-only. People can still open old links while they move to the new system.
6. Assign an owner to every important group of documents.
7. Keep docs connected to code, tickets, and other sources that show when information has changed.

Falconer's [Confluence migration walkthrough](https://falconer.com/guides/context-sovereignty-atlassian-data-policy/#migrating-from-confluence-to-falconer-takes-less-than-a-day) shows how to connect Confluence, choose spaces, review imported content, and keep documentation current.

## When should you start?

Confluence Data Center subscriptions and associated Marketplace app licenses [expire on March 28, 2029](https://community.atlassian.com/forums/Data-Center-articles/Reminder-Upcoming-changes-to-Data-Center-products/ba-p/3210679), when the product becomes read-only.
Existing customers can buy new subscriptions, expand, or upgrade only until March 30, 2028, and new customers have been unable to purchase Data Center since March 30, 2026.
Renewing your current footprint stays available until the 2029 expiry, so plan against March 28, 2029 rather than treating 2028 as the cutoff.

Start early enough to choose a destination, complete security and compliance reviews, test the migration, validate content and permissions, roll it out, and retire Confluence.
Waiting until 2029 leaves little time to fix problems without extending your contract or rushing the work.

There is another reason to start early: stale pages keep accumulating, and every extra page takes time to review.
Starting earlier means moving less outdated content ([why we think context sovereignty matters here](https://falconer.com/guides/context-sovereignty-atlassian-data-policy/)).

You do not need to plan the entire migration before starting.
[Start a Falconer trial](https://falconer.com/auth/signin?utm_source=blog&utm_medium=referral&utm_campaign=content), connect a Confluence space through the read-only integration, and see the imported content in Falconer without changing your existing instance.

## Frequently asked questions

### How long does it take to migrate off Confluence Data Center?

A manual migration can take weeks once you include review, permissions, macros, broken links, and rollout.
With Falconer, the initial import and setup can be completed within a day.
It preserves the page hierarchy, leaves the original Confluence instance unchanged, and identifies outdated, duplicate, and missing content for review.

### How long does a large Confluence Data Center migration take?

A large migration may take longer, but headcount alone does not determine the timeline.
Macros, permissions, broken links, duplicate pages, and stale content create most of the work.
Falconer handles the import and identifies what needs attention, so larger teams can focus on decisions instead of moving pages.

### Should you clean Confluence before migrating to a new platform?

Usually no.
Import first, then review the content in Falconer.
Cleaning every page beforehand can delay the move indefinitely.
Falconer lets you choose which spaces to bring over and then identifies outdated, duplicate, and missing content.

### Which Confluence pages should you migrate first?

Start with runbooks, deployment guides, architecture docs, onboarding material, API references, and current policies.
Review macro-heavy pages separately because some macros and Marketplace app content may need extra work.
Falconer preserves the hierarchy and surfaces the pages that need attention.

### When should you turn off Confluence after migrating?

Turn off Confluence after your team has validated the imported content, confirmed access, and started using the new system.
Falconer's read-only integration leaves the original instance unchanged, so Confluence can remain available as a fallback until you are ready to retire it.

### What are the most common Confluence migration mistakes?

Copying every page into another static system recreates the same stale knowledge base.
Falconer provides a complete path: it imports your spaces, preserves their structure, identifies content problems, and keeps documentation current as connected sources change.