Migrate from Freedcamp to Jira

Freedcamp Projects map directly to Jira Projects as the top-level container. Project name, description, status (active/archived), creation date, and owner transfer. Jira project type (Jira Software, Jira, or Jira Business) is selected during scoping based on the destination plan. Freedcamp's Project-level Custom Fields (Enterprise-only) migrate as Jira custom fields; the Jira custom field must be created with the appropriate Issue Type context before task import begins.

Freedcamp Tasks are the primary work unit and map to Jira Issues. Each task's title, description, assignee (resolved by email to Jira User), due date, priority, status, and created/modified timestamps transfer. Subtasks map to Jira Sub-tasks linked via the Parent Issue key. The Issue Type defaults to Task but can be split into Story, Bug, or Epic based on aFreedcamp's task categorization or a customer-defined rule agreed during scoping.

Freedcamp Milestones map to Jira Due Date on the associated Issue if the milestone applies to a single task. For cross-task milestone tracking, we create a Jira Milestone (using the project milestone field or a custom field of type Milestone) and link all tasks with that milestone. Start dates on Freedcamp Milestones transfer to the Jira Issue Start Date field if the destination Jira plan supports it.

Freedcamp Discussion boards and individual comments map to Jira Issue Comments on the target Issue. Thread structure is preserved by ordering comments chronologically; each comment's author (resolved by email), timestamp, and content transfer as a Jira Comment with the author attribution preserved. Inline images in Freedcamp comments migrate as Jira-attached files linked to the same Issue.

Freedcamp Time Entries (duration, date, user, associated task or project, and notes) map to Jira Worklogs where the Jira plan supports it (Jira Software Standard and Premium include worklogs). We resolve the Jira Issue by matching the Freedcamp task title and project to the migrated Issue key, and resolve the user by email match to the Jira User. Billable flags and hourly rates from Freedcamp Business/Enterprise transfer as custom fields on the Worklog.

Files uploaded to Freedcamp Projects, Tasks, or Discussions migrate as Jira Issue Attachments. The folder structure replicates as a flat attachment list on each Issue. File name, size, upload date, and uploader transfer. Jira Cloud requires attachments to have a non-null filename; we flag and correct any null-filename attachments before migration. Maximum attachment size respects the destination Jira plan limits (10 MB on Free, 250 MB on Standard+).

Freedcamp user accounts (display name, email, role) map to Jira Users by email match. Freedcamp Project Administrators and Group Administrators map to Jira Administrators or Project Administrators based on role scope. Freedcamp users without a corresponding Jira account are held in a reconciliation queue for the customer's admin to provision before record import.

Freedcamp tags applied to Tasks, Projects, Issues, and other objects migrate as Jira Labels. Tag strings transfer verbatim; Jira renders them as searchable labels on the Issue. Tag colors do not transfer as Jira does not support label color natively without a marketplace plugin.

Freedcamp Task-level Custom Fields (Business/Enterprise plans) require pre-creation in Jira as custom fields of equivalent type (text, number, date, dropdown, checkbox) with an explicit Issue Type context that includes the migrated Issue Types. Dropdown option values, required flags, and separators replicate as Jira field configurations. We export the custom field template schema separately during scoping and reapply it at the destination before data import begins.

Freedcamp's premium Issue Tracker module stores issues with priority, status, type, assignee, reporter, due date, and custom fields. These map to Jira Issues with Issue Type set to Bug or Task based on the Freedcamp issue type classification. Issue Tracker custom fields follow the same custom field creation and context configuration process as Task-level Custom Fields. This object is only present on Freedcamp Business or Enterprise plans.

Freedcamp Wiki pages and their content migrate as structured HTML documents. Jira does not have a native wiki capability; the destination for Freedcamp Wiki content is typically Confluence. We extract page content, inline images, and discussion threads and deliver them as a structured export. Wiki content does not auto-populate; the customer's admin or a Confluence implementation partner creates Confluence pages from the export.