Migrate from Freelo to Jira

Freelo Projects map directly to Jira Projects as the top-level container. We preserve project name, description, creation date, and status (active/archived). Jira projects require a project lead and permission scheme to be configured before migration; we coordinate with the customer's Jira admin to provision these during scoping. Freelo's archived projects migrate to Jira projects with the archived flag set via the Jira API.

Freelo To-Do Lists have no direct Jira equivalent because Jira uses a flat issue structure under projects. We present two migration strategies during scoping: Strategy A maps each Freelo To-Do List to a Jira Label (preserving grouping but requiring label-based filtering), Strategy B maps To-Do Lists to a custom Issue Type called 'Section' (enabling board column filtering). The customer selects the strategy; we document the mapping and apply it consistently across all projects.

Freelo Tasks map to Jira Issues with title, description (migrated as Jira wiki-style markup), assignee (resolved by email match to Jira User), reporter, priority, due date, created date, updated date, and completion date. Status mapping follows Freelo's status set (typically Open, In Progress, Done) to Jira status categories. Freelo task labels migrate as Jira Labels.

Freelo Subtasks are a distinct nested object type and map to Jira Sub-Task issues with a Parent Link field pointing to the migrated Jira Issue. The Freelo subtask title, assignee, status, and due date all migrate into the Jira Sub-Task fields. Jira requires Sub-Tasks to be enabled on the project; we verify this during project configuration and enable it via the Jira project settings API if needed.

Freelo users (Admin, Project Manager, Member roles) map to Jira Users by email address. We extract all users referenced in task assignments and comments, resolve by email match against the destination Jira site, and provision a reconciliation queue for any user without a matching Jira account. Jira's per-user licensing means the customer must assign a Jira seat to each migrating user; we flag the user count before migration begins.

Freelo time entries carry duration, cost value, and currency per task. On Jira Premium and Enterprise, we map these to native Worklog entries with the original timestamp and author preserved. On Jira Standard, Jira does not have native worklogging, so we migrate duration to a custom Number field (freelo_logged_hours__c) and cost to a custom Currency field (freelo_cost__c) on the Issue. The customer chooses the strategy during scoping based on their Jira plan.

Freelo attachments up to 100 MB per file migrate to Jira Attachments on the corresponding Issue. Files larger than 100 MB are flagged for manual handling because they exceed Freelo's upload ceiling and cannot be exported via API. We download the file metadata (name, caption, UUID) and re-upload the binary to Jira's attachment endpoint. Jira's attachment size limit (10 MB on Standard, higher on Premium and Data Center) may require further chunking for files approaching that threshold.

Freelo comments on Tasks and To-Do Lists migrate to Jira Comments on the corresponding Issue. We preserve comment body (with Markdown preserved as-is), author (resolved to Jira User by email), and timestamp. Comments on Freelo To-Do Lists migrate to Jira Comments on the first Jira Issue mapped from that To-Do List, with the comment body noting the original To-Do List name for audit.

Freelo custom fields on Tasks (text, number, date, dropdown) migrate to Jira Custom Fields of equivalent type. We export the field name and raw value from Freelo's API (which does not return a typed schema descriptor), create matching Jira custom fields during the schema phase, and apply values during the task import phase. Dropdown values are migrated as-is; Jira picklist validation confirms that the Freelo value is whitelisted in the destination field.

Freelo's Gmail inbox integration creates tasks from email threads with embedded assignees and due dates. This integration is a Freelo-specific workflow feature that has no equivalent in Jira and does not produce a persistent data record that can be exported. We document each Gmail-created task found in Freelo as a standard Task record with its metadata intact, but the email threading context itself does not migrate. The customer rebuilds this workflow in Jira using Jira Automation rules or Gmail-to-Jira integrations available on the Atlassian Marketplace.

Freelo's Business module (invoicing, billing, and advanced financial workflows) is gated behind paid tiers and has no direct Jira equivalent. Jira is a work management and issue tracking platform, not a billing system. We do not migrate invoices, line items, or billing records. If the customer requires invoice continuity, we recommend retaining Freelo in read-only mode for historical invoice reference or migrating invoice records to a dedicated accounting tool separately.