Fix Duplicate Fields Left by JCMA Migration

After migrating from Jira Data Center to Cloud, the Jira Cloud Migration Assistant (JCMA) creates duplicate custom fields with a "(migrated)" suffix. Migration Field Cleanup detects every duplicate and merges them safely — no scripting, no data loss.

Get It Free on Marketplace See How It Works

The Problem

The Jira Cloud Migration Assistant (JCMA) creates copies of every custom field with a "(migrated)" suffix. If you migrated multiple times, you may have "(migrated 2)", "(migrated 3)", and more. These duplicate fields cause:

User confusion from duplicate fields on issue forms
Broken JQL queries returning incomplete or unexpected results
Performance degradation from field bloat
Weeks of risky manual cleanup scripting

What Migration Field Cleanup Does

Detect Every Duplicate

Scans all custom fields and detects every "(migrated)" suffix pair. Groups by original field name and flags schema mismatches.

Safe Merge, Zero Data Loss

Copies migrated values into original fields only when the original is empty. Existing Cloud-native data is never overwritten.

Runs on Atlassian

Built on Atlassian Forge. All processing happens inside your Jira Cloud instance. No external servers, no data leaves your site.

Batch Processing

Processes issues in batches with cursor-based pagination and a live progress bar. Handles thousands of issues reliably.

Preview Before Merge

Review every field pair, safety classification, and affected issue count before committing to the merge operation.

Minimal Permissions

Only two API scopes required: read and write Jira work data. No admin-level access, no user data access.

How It Works

Install — add the app from the Atlassian Marketplace (free to install)
Scan — click "Scan for Duplicates" to detect all migrated field pairs
Review — see which fields have duplicates, safety classification, and issue counts
Merge — select field pairs, confirm, and watch the live progress bar
Done — re-scan to verify cleanup is complete

Marketplace Pricing

Pricing and licensing are managed through the Atlassian Marketplace. See the marketplace listing for current pricing, trials, and billing details.

Scanning is always free — see your duplicates at no cost
Merging requires a license purchased through the Atlassian Marketplace
The Marketplace controls billing, trials, and refunds

View on Atlassian Marketplace

Built for Safety

Only copies migrated values when the original field is empty — never overwrites
Safe to re-run — idempotent operation
Preview before merge — see exactly what will change
Built on Atlassian Forge — no external infrastructure
43 unit tests covering scanner logic, edge cases, and error paths