Migrate from Advantage to Jira

Advantage Projects map directly to Jira Projects. We preserve project metadata (name, description, key identifier) and project-level settings. Jira Projects require a Project Key (e.g., PROJ) that we derive from the Advantage project name or ID. Project-level permission schemes and notification schemes are configured in Jira before migration. If the destination Jira Cloud site already contains projects with conflicting keys, we append a suffix and document the change for the customer.

Advantage Tasks map to Jira Issues. Each task becomes an Issue of a configured Issue Type (Story, Task, or Bug). The Advantage task name becomes the Jira summary, status maps from the source status to a Jira Status in the target project's workflow, and the due date maps to the Due Date field. We preserve the Advantage task description as the Jira description (converted to Jira's wiki-markup or ADF format as appropriate). Priority is mapped using a configured mapping table (Advantage priority levels to Jira Priority IDs). Subtasks in Advantage map to Jira Subtasks linked via the Parent Issue key.

Advantage custom objects defined in Schema Manager map to Jira custom objects. We pre-create the destination schema in Jira Cloud including all custom fields, pick list values, and relationship fields before any data import. Jira custom object naming follows the __c suffix convention. If the custom object has lookups to Projects or Issues, we configure the appropriate Context before migration. Jira Cloud Data Center edition supports custom objects; standard Jira Cloud also supports them from Standard tier onward.

Advantage custom fields defined via Schema Manager map to Jira custom fields of the equivalent type: text fields to Jira Text Field (single-line), long text to Jira Text Field (multi-line), date fields to Jira Date Picker, numeric fields to Jira Number Field, and pick list fields to Jira Select List (cascading or single). We flag any Advantage field types that Jira does not natively support (e.g., complex computed fields) and document them for manual handling. Jira Cloud has a known performance degradation at 200+ custom fields per instance per Atlassian's own scaling documentation; we warn if the Advantage schema exceeds this threshold.

Advantage file attachments linked to records are exported from the source and re-uploaded to the corresponding Jira Issue. Attachment file names, sizes, and MIME types are preserved. We create the file attachment in Jira using the Attachments REST API endpoint. The link to the parent Issue is resolved at migration time using the Advantage record-to-Jira Issue key mapping. Jira Cloud's free plan includes 2 GB of shared file storage; larger attachment sets may require a Jira Cloud paid plan to accommodate increased storage limits.

Advantage user records map to Jira Cloud users. We match by email address as the primary key. User display names, email addresses, and active/inactive status are imported. Jira Cloud user management is administered in the destination site; we require the customer to provision the Atlassian account for each user before migration. Users without a match in Jira are held in a reconciliation queue for the admin to resolve before the import phase begins.

Advantage task assignments (which user a task is assigned to) map to Jira Issue Assignee. We resolve the Advantage assignee user ID to the corresponding Jira Cloud user via the email-based user mapping. Unassigned tasks in Advantage map to unassigned issues in Jira. If a Jira project has a default assignee configured (e.g., the project lead), we apply it for any unresolved owner references.

Advantage comments on tasks and projects migrate as Jira Comments on the corresponding Issue. Author, timestamp, and comment body are preserved. Comment body is converted to Jira's ADF (Atlassian Document Format) to preserve formatting where possible. If Advantage comments contain embedded images or file references, we migrate those as Jira attachments linked to the Issue and update the comment body with the new attachment link.

Advantage automation rules and workflow assignments do not migrate to Jira as executable configurations. Jira workflows use a different model: Status, Transitions, Validators, and Post-Functions configured in Workflow Designer and attached to Issue Types via Workflow Schemes. We deliver a written inventory of every active Advantage automation rule with its trigger, conditions, actions, and a recommended Jira automation equivalent. Jira's native Automation Rules (available from Standard plan) and community marketplace apps (Automation for Jira, JMWE) are common rebuild targets.

Advantage record creation and modification timestamps are preserved in Jira's Created and Updated system fields on every migrated record. Jira Cloud sets these fields at insert time by default; we override them using the Created and Updated field support in the Jira REST API so that the original Advantage timeline is accurate. This is critical for reporting, SLA tracking, and audit history in the destination.

Advantage project-level settings including default view, notification preferences, and project-specific custom field defaults map to Jira Project Settings. We configure the Jira project type (team-managed or company-managed), default Issue Type scheme, workflow scheme, field configuration scheme, and notification scheme before migrating any Issues. Settings are deployed via the Jira REST API or bulk-configured in the Jira project settings UI.