Confluence Data Center Diagram Migration to Cloud

Q: Can diagram.now import an old Visio .vsd file?

Not directly. The current importer accepts .vsdx. Convert the source in a compatible Visio version, keep the original .vsd, and compare the converted file before migration.

Q: Will every imported file look pixel-perfect?

No. Complex vendor-specific features, custom shapes, and unsupported objects can be simplified or skipped. Keep original files and verify representative imports before committing to a migration.

Q: Does the browser preflight upload my file?

Supported imports in the free editor are parsed in the browser. Emailing a sample for one-file help is a separate path, so send only a non-sensitive or sanitized file.

Start with the app assessment

Your Confluence migration plan and your diagram migration plan are related—but not identical.

Atlassian’s Confluence Cloud Migration Assistant assesses Marketplace apps and shows whether an app has a Cloud version and migration path. Atlassian also lets you mark an app as not needed or choose an alternative. That decision is the start of diagram migration, not proof that every embedded diagram will arrive editable.

1. Inventory the macros

Record the current diagram app, page count, owners, source-file location, and whether the diagram must remain editable or can be archived as an image.

2. Read the app status

In the assistant, distinguish an automated path from Contact vendor, No, or an intentional Use alternative decision. Do not infer support from a Cloud listing alone.

3. Prove the hard cases

Test complex and multi-page files before the migration freeze. Verify labels, connections, custom imagery, layers, and any warning—not just whether the file opens.

A file-first runbook

A defensible migration in six checks

Use a representative sample to decide the route for each source family, then apply the approved route to the rest of that family.

Audit apps and owners

Export the Cloud Migration Assistant assessment. For each legacy diagram macro, name an owner and capture the vendor’s migration status before choosing an alternative.

Preserve originals

Keep the Data Center page export and original editable source. An image is useful evidence, but it is not an editable migration source.

Choose representative files

Pick at least one simple, one complex, and one multi-page file per format. Include custom shapes or embedded images if those appear in production.

Run a compatibility preflight

Use the free browser editor or ask us to test one sanitized file. Check the imported pages, objects, connectors, labels, and warnings.

Import inside Confluence Cloud

Install diagram.now, add it to a Cloud page, and run the same supported import. Save, close, reopen, and make a small edit to prove the result is live—not a screenshot.

Reconcile and sign off

Compare the Cloud page with the source, retain an exception list, and get the content owner’s approval before the Data Center copy becomes read-only.

Current importer coverage

What can become editable—and what needs caution

These are diagram.now’s current, deliberately narrow import contracts. Vendor-specific features outside them may be simplified or skipped.

Source	Give diagram.now	Editable result	Migration note
Microsoft Visio	`.vsdx`	Pages, supported shapes, labels, connectors, and supported images	Legacy `.vsd` is not accepted. Convert to `.vsdx` first. Custom masters, nested sub-shapes, and specialized objects need visual review.
Lucidchart	`.lucid` archive	Pages, mapped shapes, text, links, and connectors	The archive must contain Lucid’s document data. Keep the source; unsupported types can be mapped to simpler editable shapes.
Gliffy	`.gliffy` export	Supported objects, text, shapes, and connections	Export the editable Gliffy format—not PNG, JPG, or SVG—when editability is the goal. Review any importer warnings.
Mermaid	Paste `flowchart` or `graph` source	Editable nodes, edges, directions, subgraphs, and supported edge labels	Only flowchart/graph syntax is promised. Sequence, class, state, ER, Gantt, and other Mermaid diagram families are outside the current importer contract.
SQL schema	Paste `CREATE TABLE` DDL	Editable ERD entities plus primary/foreign-key relationships	This is schema-to-ERD conversion. Stored procedures, queries, data, and vendor-specific database behavior are not migrated.
Saved diagram.now file	`.diagramly`, JSON, or diagram.now XML	Native pages, shapes, and connectors	PNG, SVG, and PDF reopen as editable only when diagram.now created them with embedded source. A flattened third-party export stays flattened.

What this page does not claim

It does not promise direct draw.io/mxGraph conversion, automatic macro replacement, bulk migration, or pixel-perfect fidelity. Use the installed app’s documented path when one exists; use representative-file testing when you choose an alternative.

A real migration check

Send one non-sensitive file. Get a compatibility answer.

Tell us the source format and what must remain editable. We’ll test one representative file and reply with what imported, what needed cleanup, and whether the current route is suitable. No sales deck is required.

Ask us to test one file Test it yourself first

Current Atlassian Marketplace pricing

Start on the $0 app tier for up to 10 users.

Pricing below is the diagram.now Cloud app price shown by Atlassian, not the price of your Confluence subscription. Fact-checked against Atlassian’s live Marketplace price table on July 19, 2026.

$01–10 users · diagram.now Cloud appMonthly or annual entry in the current Marketplace table.

Two useful planning examples

15 users: $142.50 USD/year
50 users: $475.00 USD/year

Atlassian bills the app against the host-product user tier and may display local currency, tax, or later pricing changes. Verify the live price before purchase.

View or install on Marketplace Check Atlassian’s live price table

Migration FAQ

Questions to settle before cutover

Will the Confluence Cloud Migration Assistant migrate every diagram app automatically?

No. Marketplace app migration is app-specific. Use the assistant’s app assessment to confirm whether an automated path exists. Depending on the result, Atlassian may direct you to upgrade, contact the vendor, mark the app not needed, or choose an alternative.

Can diagram.now import an old Visio .vsd file?

Not directly. The current importer accepts .vsdx. Convert the source in a compatible Visio version, keep the original .vsd, and compare the converted file before migration. Microsoft identifies .vsdx as the editable drawing format for Visio in Microsoft 365.

Will every imported file look pixel-perfect?

No. Imports prioritize an editable result, and complex vendor-specific features, custom shapes, nested objects, or unsupported elements can be simplified or skipped. Preserve the source, read warnings, and have a content owner approve representative examples.

Does the browser preflight upload my file?

Supported imports in the free editor are parsed in your browser. The optional one-file help path is different: emailing a sample sends it through email, so use only a non-sensitive or sanitized file and never send confidential material.

Can I directly import draw.io or mxGraph files?

Not through the migration workflow documented on this page. Do not rename a draw.io file and assume compatibility. Keep the original and use the one-file help CTA if you want us to inspect a representative file and explain the current options.

Is the Confluence app really free for up to 10 users?

Yes. Atlassian’s live price table currently lists the diagram.now Cloud app at $0 for the 1–10 user tier. This is app pricing; your Confluence plan is separate. The same table currently lists $142.50/year for 15 users and $475/year for 50 users.

Primary-source notes

Facts checked at the source

Deadlines and platform behavior change. These are the current first-party references used for this guide, checked July 19, 2026.

Continue the evaluation