Migrate from Freedcamp to monday Work Management

Freedcamp Projects map to monday.com Boards as the top-level container. We extract project title, description, status, ownership, and dates and load them as Board metadata. If the Freedcamp plan is Free or Pro (no Project Custom Fields), the Board is created with default columns; if Business or Enterprise, the Project-level Custom Field template is read and equivalent monday.com column types (Text, Number, Date, Status, Dropdown) are configured on the Board before Items are imported. We flag any Enterprise-tier custom field types not natively supported by the destination monday.com plan (Formula columns require Pro) for manual column adjustment post-migration.

Freedcamp Tasks map to monday.com Items on the corresponding Board. Title, description, assignee, due date, priority, and status transfer directly. Task Custom Fields (Business/Enterprise on Freedcamp) map to monday.com column types — Dropdown options become Status or Dropdown columns, dates become Date columns, text values become Text columns, and numeric values become Number columns. Required flags and drop-down option lists are preserved as monday.com column configuration. Subtasks on Freedcamp map to monday.com Subitems on the parent Item, with their own title, assignee, and due date preserved.

Freedcamp Subtasks nested under Tasks map to monday.com Subitems attached to the parent Item. Each Subitem inherits a link to the parent Item, with its own title, assignee, due date, and status transferred. This mapping requires the parent Task-to-Item migration to complete first so that Item IDs are available for Subitem parent references. monday.com's Multiple Layers view can be configured post-migration to display Subitems in a Gantt or board layout if the team requires a visual hierarchy.

Freedcamp Milestones are standalone deadline markers with a title, target date, and completion status. We map these to monday.com Items in a dedicated Milestones group on the board, with the target date stored in a Date column or Timeline column and completion status reflected in a Status column. Nested Milestone hierarchies (if used on Freedcamp Enterprise) do not have a direct monday.com equivalent and are flattened — parent-child relationships are preserved in a Text column as a reference string until the admin rebuilds the structure using monday.com's board-linking features.

Freedcamp Discussion threads per project map to monday.com Updates attached to Items. The original thread structure with comments, timestamps, and author attribution migrates as a chain of Updates on the Item representing the Discussion topic. Comment ordering is preserved chronologically. Note that monday.com Updates use a different formatting model than Freedcamp threaded comments; we preserve text content, inline links, and @mentions, but rich formatting differences are flagged in the reconciliation report for spot-check by the project manager.

Freedcamp Calendar Events (start/end datetime, recurrence rules, associated project) map to monday.com using an Events column or Items with Start Date and End Date columns. Recurrence patterns from Freedcamp do not carry over automatically — the Events column supports date ranges and grouping but not native recurrence rules. File attachments linked to calendar events migrate as Item file attachments. Google Calendar sync settings from Freedcamp Pro are not replicated; the admin reconfigures calendar integration in monday.com Settings post-migration.

Freedcamp Time tracking entries (duration, date, associated task or project, user, notes) map to monday.com's Time Tracking column on the corresponding Item. The Date and Duration fields transfer as-is. Notes attached to the time entry are stored in a Text column on the Item alongside the time column. This mapping requires the Item parent record to exist first, so time entries are migrated after the parent Task-to-Item migration phase completes. monday.com's Time Tracking feature is available on Standard and above — we flag this at scoping if the destination plan is Basic.

Freedcamp Issue Tracker (Business/Enterprise premium app) records migrate as Items on a monday.com board structured for issue management. Priority, status, type, assignee, reporter, due date, and any custom fields transfer as monday.com column values. Issue Tracker-specific G2 integrations and labels do not migrate — these map to monday.com Labels and column values respectively. If the customer used Jira-style issue labels or linked issues across projects via Freedcamp's cross-project link feature, those cross-references are preserved in a Text column as a reference string for the admin to rebuild using monday.com's board-connecting features.

Freedcamp Wiki pages (Business/Enterprise premium app) migrate to monday Docs boards. Each wiki page becomes a Doc page in a Docs board, with page title, content, and inline discussions preserved. Version history metadata migrates as a structured list attached to the page. Freedcamp wiki-specific formatting (if any) is converted to monday Docs native formatting. Inline G2/Capterra integration links do not carry over and are flagged for manual reconnection in monday.com if needed.

Freedcamp Invoices+ records (line items, totals, client association, status) migrate as Items on a monday.com board structured for billing records. monday.com has no native invoicing or billing module — invoice generation, payment tracking, and client payment links are not replicated. We flag this gap in the scope document and recommend pairing monday.com with Stripe, Qoyod, or QuickBooks for billing workflows. The monday.com board holds operational billing data (client, amounts, due dates, status) while the dedicated billing tool handles invoice PDF generation and payment collection.

Freedcamp Task-level Custom Fields (Business/Enterprise) and Project-level Custom Fields (Enterprise) migrate as monday.com column configurations. Dropdown options become Status or Dropdown columns; date fields become Date columns; numeric values become Number columns; text values become Text columns; checkbox values become Checkbox columns. Required flags and separator lines do not have direct equivalents and are noted in the template schema export for the admin to reapply manually. Custom field templates themselves are exported as a schema document separate from the data and handed off for reapplication.

Tags and Labels applied to Freedcamp Tasks, Projects, Issues, and other objects migrate as monday.com Labels attached to Items. Label names and color coding transfer where supported by the monday.com API. Multi-tag assignments on a single Freedcamp record map to multiple monday.com Labels on the corresponding Item. This is a straightforward string-value migration; no structural transformation is required beyond splitting comma-separated tag lists into individual label assignments.

Freedcamp user accounts (display name, email address, role assignment) migrate as monday.com workspace members. We match by email address and flag any Freedcamp user without a matching monday.com account for manual provisioning before cutover. Freedcamp's Group Administrator delegations and Enterprise permission sets do not map to monday.com's board-level permission model — we export the role matrix as a written document for the admin to reassign board owners and viewers post-migration.

Files uploaded to Freedcamp Projects, Discussions, Tasks, or Calendar Events migrate as binary attachments to the corresponding monday.com Items. We replicate the folder structure as a naming convention prefix on the file name (e.g., ProjectName_TaskName_filename.pdf). File metadata (original upload date, uploader name, file size) is preserved in a companion CSV for reconciliation. File size limits differ: Freedcamp Free caps at 10 MB per file, Freedcamp Pro at 25 MB; monday.com Pro+ allows up to 250 MB per file. Files exceeding the destination plan limit are flagged for the admin to store in a linked Google Drive or Dropbox folder instead.