Migrate from Agilean to Jira

Agilean Projects map directly to Jira Projects. We create the Jira Project in the target site (Cloud or Data Center) before any issue migration, using the Project Key derived from the Agilean Project name's initials or customer-specified key. Project Lead maps to Jira Project Lead role. Jira Project type (team-managed or company-managed) is decided during scoping based on the customer's governance model.

Agilean Tasks map to Jira Issues with the issue type determined during scoping. If Agilean Tasks have sub-tasks, those map to Jira Sub-tasks with the parent Issue resolved by a name-match lookup. Epic-level Agilean Tasks (identified by a naming convention or a custom field flag) map to Jira Epic Issues. We use Jira's REST API issue creation endpoint with the project key and issuetype field set per record.

Agilean's flexible key-value pairs require type inference during discovery. We map Agilean text properties to Jira Text Field (single line) or Text Area (multi-line), date properties to Jira Date Picker, numeric properties to Jira Number Field, boolean flags to Jira Checkbox, and list-type values to Jira Select (single) or Multi-Select. Jira Custom Fields are pre-created in the target project before data import using the Jira REST API custom fields endpoint. Fields without a clear Jira equivalent are flagged in the discovery report for customer decision.

Agilean file attachments migrate to Jira Issue Attachments using Jira's REST API attachment endpoint. Files are uploaded as binary blobs with the attachment linked to the parent Issue ID resolved during the task migration phase. Large attachment sets (over 50 GB total) require chunking and may extend the migration timeline. We preserve original filenames and content types where available from Agilean.

Agilean task assignee references map to Jira User records by email address lookup. We extract all distinct assignee values from Agilean and match them against the Jira site's user directory. Any Agilean assignee without a matching Jira User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Jira users are supported for assignee mapping if the customer requests historical preservation.

Agilean task status values (e.g., To Do, In Progress, Done, Blocked) map to Jira Status values within the target project's workflow. We map each Agilean status to the corresponding Jira Status Name and verify that the Jira workflow's status category (To Do, In Progress, Done) is assigned correctly. Statuses that do not exist in the Jira workflow are created during configuration before import begins.

Agilean priority values map to Jira Priority levels (Highest, High, Medium, Low, Lowest). We establish the mapping during scoping based on the Agilean priority scale and configure the Jira Priority field accordingly. If Agilean uses a numeric priority (1-5), we map to the closest Jira Priority label.

Agilean task due dates migrate directly to Jira Issue Due Date (duedate field). We handle date-only versus datetime formats by normalizing to Jira's expected format during the transform step. Issues without due dates remain null in Jira.

Agilean record creation and update timestamps migrate as Jira Issue Created and Updated fields. Jira's REST API supports setting created via bulk import; for standard API inserts we preserve the original timestamp in a custom field original_created_date__c for audit purposes since Jira sets Created to the import time by default.

Agilean tag or label properties map to Jira Labels on the Issue. Labels are migrated as a comma-separated string applied via the labels field in Jira's issue creation payload. We deduplicate labels during transform.

Agilean workflow configurations (status transitions, approval gates, custom workflow rules) are enumerated during discovery but not migrated as code to Jira. We deliver a written inventory of each Agilean workflow with its triggers, conditions, and actions mapped to a recommended Jira Workflow XML structure. The customer's Jira admin rebuilds the workflow in Jira's workflow designer. This is standard scope for all FlitStack AI migrations.