Migrate from Freedcamp to Trello

Freedcamp Projects map directly to Trello Boards. Project name, description, status (active/archived), and ownership transfer as Board name, description, and member invite. Freedcamp's per-project settings (notifications, permissions) map to Trello's Board settings and member roles. We use the Trello Boards API to create each board and apply members by email resolution against Trello workspace members. Archived projects in Freedcamp map to archived Trello boards.

Freedcamp Tasks map to Trello Cards. Each card is created in the List corresponding to the Freedcamp task status (Backlog, In Progress, Completed, or a custom named column). Task title, description (rich text), due date, priority, assigned user (resolved by email), and start date migrate directly. The Card description preserves hyperlinks and basic formatting from Freedcamp's HTML-formatted descriptions.

Freedcamp subtasks are nested task records under a parent Task. Trello does not support nested cards as a native object; instead, subtasks become Checklist items on the parent Card. We flatten the Freedcamp subtask tree into a single Checklist per Card, preserving title, due date (as a checklist item note), and completion status. Subtask-assigned users and priority flags are appended to the checklist item text string. Deep nesting (subtasks of subtasks) is supported: we create nested checklist items with a dash-prefix convention for visual hierarchy.

Trello has no native milestone object. We migrate Freedcamp Milestones as Cards on a dedicated Milestones List (created at the top of every board) with the milestone title as card name, milestone description in the card description, and milestone due date set as the card due date. We apply a Milestones label (color-coded per milestone category if multiple exist) so milestone cards are visually distinguishable. Completion status is preserved as card completion (moving to Done List or archiving).

Freedcamp Discussions are per-project threaded conversations. We migrate discussion threads as Card Comments on the associated project Card, preserving the thread structure by nesting comments chronologically. Author attribution and timestamp migrate as the comment author and post time. Inline images in discussion posts migrate as Card attachments with a reference in the comment body. If no associated Card exists for a discussion topic, we create a placeholder Card named after the discussion title and attach the full thread as a comment.

Freedcamp Time Entries have no Trello equivalent as native objects. We export all time log data (duration, date, associated task, user, billable flag, notes) as a structured CSV attached to the relevant Card. We also deliver a written Butler recipe: a command card template and trigger rule that recreates time logging within Trello using Card custom fields (Duration, Billable) and Butler date commands. The customer enables the Custom Fields Power-Up and applies the Butler rule post-migration to restore active time logging.

Freedcamp Calendar Events (recurring and non-recurring) map to Trello Cards with due dates and the Calendar Power-Up enabled. Event title, start/end datetime, recurrence rule, and associated project migrate. Recurrence is not a native Trello concept; we convert standard recurrence patterns (daily, weekly, monthly, yearly) into individual Cards with sequential due dates, up to 12 occurrences, and flag the last card with a recurring-handbrake label to prevent infinite generation. Google Calendar sync from Freedcamp does not replicate to Trello without manual reconnection in Trello settings.

Freedcamp Tags applied to Tasks, Projects, Issues, and other objects migrate to Trello Labels. We replicate the tag color scheme where Freedcamp exposes it; otherwise we assign a default color palette across the label set. Label names migrate verbatim. Trello supports up to 50 labels per board, which accommodates most Freedcamp tag sets; we flag any account exceeding 50 distinct tag values during scoping.

Freedcamp Task Custom Fields (Business/Enterprise only) map to Trello Custom Fields via the Trello Custom Fields Power-Up API. The Power-Up must be enabled on each destination board before we can write field definitions. We create Custom Field definitions per board (text, number, date, checkbox, dropdown) matching the Freedcamp template schema, then write values per Card. Dropdown options from Freedcamp become Trello dropdown Custom Field options. If the customer has not enabled the Custom Fields Power-Up on all boards, we configure it as a pre-migration step.

Freedcamp Project Custom Fields (Enterprise only) have no clean single-board Trello equivalent because project-level attributes in Trello live on individual Cards. We map project Custom Fields to a Board Information Card (a dedicated Card titled Project Metadata) with Custom Fields or description text holding the original values. We also export the full project Custom Field template schema as a companion CSV for manual reference.

Freedcamp User accounts (display name, email, role per project) resolve by email match against Trello workspace members. We invite any Freedcamp user not yet in the Trello workspace before record migration. Freedcamp role permissions (Project Administrator, Group Administrator, standard user) do not map directly to Trello roles; we set all migrated members as normal Board Members and document the Trello Workspace permission model for the customer's admin to reconfigure admin-level access post-migration.

Freedcamp Files uploaded to Projects or Discussions migrate as Card attachments on the relevant Card. File name, size, upload date, and uploader metadata are preserved. We replicate the folder structure as Card attachment descriptions for reference. Freedcamp's file size limits vary by plan (10MB Free, 25MB Pro, 100MB Business, 250MB Enterprise); we verify file sizes against the source plan's limit and flag any oversized files before attempting attachment migration.