Migrate from ActiveCollab to Jira

ActiveCollab Projects map directly to Jira Projects. Each Jira project requires a Project Key (2-10 uppercase alphanumeric characters) derived from the source ActiveCollab project name. We configure the Issue Type Scheme at migration time: Jira Software for software development teams (Bug, Story, Task, Epic, Sub-task), Jira for operational teams (Task, Story, Bug), or a blended scheme. Project category, budget fields, and owner assignment from ActiveCollab map to Jira Project properties and the Project Lead field.

ActiveCollab Tasks map to Jira Issues with type determined during scoping. Tasks with a software development context map to Jira Story or Bug; tasks with an operational or agency context map to Jira Task. Jira's summary, description (stored as Jira's Description field with Atlassian Document Format), assignee, reporter, priority, due date, and status all have direct field-level equivalents. Task order within lists migrates to Jira's Rank field (premium) or is preserved via positional metadata in a custom field if the Jira project is on Standard tier.

ActiveCollab Subtasks map to Jira Sub-task issues, which require Sub-task issue type to be enabled on the destination Jira project. We preserve the parent-child relationship by setting the Parent field on each Sub-task to the migrated Jira Issue key at migration time. The assignee, due date, and completion status of each Subtask transfer directly. Sub-task rank follows the parent Task's rank ordering.

ActiveCollab Discussions are threaded comment threads attached to Projects or Tasks. They map to Jira Comments on the corresponding Issue with author, timestamp, and rich-text body preserved. Jira stores comments in plain text or Atlassian Document Format; we convert HTML-formatted discussion content accordingly. Discussion threads that were attached to Projects with no linked task are attached to the migrated Project's default issue if a default issue exists, or documented as a separate manual-action item.

ActiveCollab Notes are free-form text records at the Project level with no Jira or Jira Software equivalent. We handle this gap in two ways: Notes that document a specific task become part of that Task's Description field (prepended with a '--- Migrated Note ---' separator), and Notes that document the Project as a whole are attached as a text file to the Jira Project via an initial Issue used as a container. The customer chooses the strategy during scoping.

ActiveCollab Time Entries with billable flag, job type, and duration map to Jira Worklog records on the corresponding Issue. The time spent value migrates as Jira's timeSpent (in seconds), the worklog start date from the original ActiveCollab timestamp, and the billable flag to Jira's billableFlag (available on Jira Software Premium). Job type maps to a custom Jira text field job_type__c for reporting. Timesheet rollup from ActiveCollab does not migrate as a Jira report; it is reconstructed post-migration using Jira's Time Tracking reports.

ActiveCollab Members (paid seats) and Clients (free collaborators) both map to Jira Users. We match by email address as the dedupe key. ActiveCollab Members without a matching Jira user go to a reconciliation queue for the customer's admin to provision before record migration. Member role (admin, member, client) maps to Jira project roles: Member to Developer or Contributor, Client to Customer (if Jira Service Management is in scope). Archived ActiveCollab members map to Jira users with active=false.

ActiveCollab Labels are tag strings applied to Tasks and Projects for filtering, and they map directly to Jira Labels. We preserve the full label vocabulary (colors, if used) and reapply label assignments to migrated Issues. Jira Labels are a global field with no pre-creation required; Jira creates them on first use. If the customer uses a structured label taxonomy (e.g., client::category::tag), we preserve it as-is and note that Jira's label autocomplete will surface them in the same format.

Files uploaded to ActiveCollab via the /upload-files API and referenced by UUID are downloaded to FlitStack AI staging storage, then re-uploaded to the corresponding Jira Issue via the Jira REST API /rest/api/3/issue/{issueIdOrKey}/attachments. We preserve the original filename, content type, and upload timestamp. Attachments linked to Projects without a specific task are attached to the default Jira project container issue.

ActiveCollab Project Templates bundle a named set of Tasks, Subtasks, and Discussions. We migrate the template structure as a new Jira Project with a naming convention indicating its template origin (e.g., '[Template] Project Name'). The template tasks and subtasks are imported as Jira Issues without assignees or due dates, ready for the customer's team to populate. Templates are not Jira's native project templates; the customer's Jira admin can create a proper Jira project template from the migrated project post-migration.

ActiveCollab finish-to-start task dependencies map to Jira Issue Links with type Blocks or Is blocked by. We reconstruct the dependency graph from ActiveCollab's dependency records and create Jira IssueLink records during migration. The directionality is preserved: if Task A depends on Task B (B must complete before A), Jira Issue B Blocks Issue A. This mapping requires Blocks/Is blocked by issue link types to be enabled in the destination Jira project configuration.

ActiveCollab Expense records (amount, category, date, receipt attachment reference) have no native Jira equivalent. We create a dedicated Jira project (e.g., 'Expenses') and migrate each expense as a Jira Issue with a custom field expense_amount__c, expense_category__c, expense_date__c, and receipt attachment. The original Project association is stored in a custom field project_ref__c for reporting and filtering.