+++ Deep Clone for Jira, External Data for Jira Fields and Quick Filters for Jira are now Atlassian Enterprise Certified +++

DEEP CLONE FOR JIRA · CLOUD-TO-CLOUD MIGRATION

Migrate Jira projects between Cloud instances

Deep Clone makes it easy to migrate projects, work items, and full hierarchies from one Jira Cloud instance to another.

Cloning Jira work items to another instance with Deep Clone for Jira

Atlassian Enterprise Certified · SOC 2 Type II · Atlassian Government Cloud · Platinum Marketplace Partner

Moving Jira shouldn't mean losing so much

CSV imports make structure hard to preserve

Export, remap, import, troubleshoot. Hierarchies and links need to be carefully rebuilt — with the right parents, IDs, link types, and directions.

Manual rebuilds drag on for months

Recreate everything by hand in the new instance and ask teams to leave their past work behind. Two months in, half the work still lives in the old cloud.

Big-bang cutovers freeze the business

Change freezes, a weekend cutover, a rollback plan nobody wants to test. Until then: two instances, two sources of truth.

Cross-instance migrations made easy

Migrate structured work directly between Jira Cloud instances in just three easy steps.

Connect the instances

Install Deep Clone on the source and target Jira Cloud sites and connect them once. Initial setup requires admin access to both instances.

Source and target Jira Cloud instances connected for cross-instance cloning

Choose what moves

Clone a whole Jira space with supported configuration, use Bulk Clone to select multiple work items, or Epic/Tree Clone to migrate complete hierarchies.

you choose what moves to the other instance

Migrate with values remapped

Deep Clone maps supported fields between instances and flags differences that need attention. Detailed logs let you verify what moved and investigate warnings or errors.

Jira field values mapped, with successful mappings checked and a difference flagged for review.

One migration engine across the enterprise

M&A CONSOLIDATION

Consolidate instances after an acquisition

Move acquired projects into the target instance with the flexibility to adapt work items as you migrate, helping teams transition faster.

Acquired company Jira projects transferred into an existing target instance

INSTANCE SPRAWL

Merge the instances that grew apart

Regional sites, departmental clouds, the instance someone spun up in 2021 — consolidate them into one source of truth.

Projects from two Jira instances consolidated into a target instance, with work item adjustments during migration.

DIVESTITURE · REORG

Split an instance during a divestiture or reorg

When a business unit, region or subsidiary needs its own Jira Cloud site, move its projects and work without rebuilding the new environment from scratch.

Acquired company Jira projects transferred into an existing target instance

What about other migration methods?

ATLASSIAN MIGRATION TOOLING

A serious option for platform-level moves

Atlassian’s native tooling transfers Jira projects and associated data between Cloud sites, including selected projects — include it in your evaluation for platform-level moves. Deep Clone adds more flexibility with granular work-item selection, field mapping with visibility into differences, and the ability to adjust field values as part of the migration.

CSV EXPORT/IMPORT

Fine for field values. Harder for hierarchies.

CSV moves field values, but preserving structure takes extra work. Parent-child relationships and links need to be carefully mapped and reconstructed during the import.

REBUILDING IN THE TARGET

Starting fresh costs more than it looks

Recreating projects in the new instance means leaving past work behind, rebuilding links, and starting reports from scratch. You lose more than time — you lose valuable context.

Built for the migrations you can't afford to get wrong

Scale

Bulk-migrate up to 100,000 work items in a single job, including projects, epics, and full hierarchies.

Audit trail

Clone History records what moved, what succeeded, and what needs attention.

Transformation

Field values remap in transit, so migrated work fits the target instance’s fields and workflows on arrival.

Security

SOC 2 certified, Atlassian Enterprise Certified, Cloud Fortified, and a participant in Atlassian’s Marketplace Security Bug Bounty Program.

The app Atlassian trusts for its own cloning

When Atlassian needed to move its own structured work between Cloud instances, Deep Clone carried the load — the bulk of the heavy lifting, finished in under a day, with nothing rolled back.

~6 months

of work saved

< 1 day

migration completed

Zero

rollbacks

Make the smart move

Install Deep Clone, connect your instances, and migrate your first project today.

Frequently asked questions

Can I migrate a Jira project from one Cloud instance to another?

Yes. Connect the target instance, choose what to move, and Deep Clone migrates work items, hierarchies, or whole projects between Jira Cloud instances — remapping field values in transit, with logs to verify the result.

Can Deep Clone migrate Jira Data Center to Jira Cloud?

No. Deep Clone migrates within and between Jira Cloud instances. For a Data Center-to-Cloud move, use Atlassian's migration tooling; then, use Deep Clone for the selective consolidation and restructuring work once you're there.

What data comes along with the migration?

Deep Clone supports broad Jira work-item data coverage, including descriptions, custom fields, comments, attachments, checklists, links, and other supported data. Exact coverage depends on the clone type and configuration, so check the compatibility documentation for migration-specific requirements.

Do field values transfer to the new instance correctly?

Deep Clone remaps field values in transit so migrated work fits the target instance's configuration. Exactly which values can be remapped depends on the field types involved — see the documentation for details.

How much can I migrate at once?

Up to 100,000 work items in a single job, running in the background with progress tracking — bulk migrations don't block anyone's work.

Do teams have to stop working during the migration?

No freeze window is required by Deep Clone: you migrate project by project while both instances stay live. Plan the sequence so each team switches over once its work has moved.

Does Deep Clone keep the two instances in sync?

No — by design. Deep Clone clones and moves structured work; it doesn't maintain a live, continuous sync between copies. If you need ongoing two-way synchronization, that's a different job than migrating structure.

More ways teams use Deep Clone

Turn any Jira project into a template

Standardize client delivery, onboarding, and recurring cycles with reusable project templates.

Explore project templates →

Everything Deep Clone does

Bulk cloning, migration, automation, and more.

See the product page →

How Deep Clone compares

Scale, reliability, setup — side by side with other cloning apps.

Compare the apps →