Hello Atlassian Community,
If you have ever planned or executed a phased, multi-wave, or multi-instance consolidation migration from Jira Server or Data Center to Jira Cloud, you know the post-migration headache: duplicated custom fields, workflows, and schemes cluttering your target Cloud site with (migrated) suffixes.
Today, we are thrilled to announce that Config Entity Deduplication for the Jira Cloud Migration Assistant (JCMA) has officially entered OPEN Beta! 🎉
❓ What Problem Does It Solve?
When migrating multiple projects or instances over time, shared Jira configurations—such as custom fields, workflows, issue type schemes, and permission schemes—are frequently re-created in Cloud.
This often leads to:
- Cloud Instance Bloat: Hundreds (or thousands) of redundant duplicate schemes and fields.
- Heavy Admin Overhead: Countless hours spent manually auditing, deleting, or merging duplicated configurations post-migration.
- User Confusion: Inconsistent configuration states across teams and a messy Day-1 Cloud experience.
Config Deduplication tackles this head-on. It detects duplicate configurations before data moves and reconciles them deterministically—ensuring your Cloud instance remains clean, standardized, and duplicate-free right from the start.
🛠️ How to Get Started
Config Deduplication is available in Open Beta via feature enablement. To join the beta:
Simply reach out directly to your MSE to enable the feature flag for your migration.
📚 Official Resources & Documentation
To learn more about configuration resolution rules and step-by-step procedures, explore our official guides:
