Migrate from Freedcamp to Asana

Freedcamp Projects map directly to Asana Projects. Project title, description, status (active/archived), ownership, and creation date migrate. Project Custom Fields (Enterprise tier only on Freedcamp) migrate as field values but the field template itself must be re-created in Asana project settings since Asana defines Custom Fields per project. We export the Custom Field template as a JSON schema and flag it for manual reapplication in each destination project.

Freedcamp Tasks map to Asana Tasks within the destination Project. We preserve title, description (rich text), due date, start date, priority, assignee, status (complete/incomplete), and created/modified timestamps. Freedcamp's Task Custom Fields (Business/Enterprise on source) map to Asana Custom Fields; we export the template schema separately and flag it for manual reapplication. Tasks without a matching Custom Field definition in Asana are logged in a companion CSV.

Freedcamp Subtasks are represented by indent levels in the task hierarchy. Asana has a dedicated Subtask object nested below a parent Task. We detect the indent pattern in Freedcamp (typically Type field showing Task, |-Subtask, |--Subtask for nested levels) and create Asana Subtask records linked to the parent Task. Subtask assignees, due dates, and status all migrate. Depth beyond two subtask levels is preserved as sequential Subtask objects in Asana.

Freedcamp Milestones map to Asana Milestones within the same Project timeline. Milestone title, due date, description, and completion status migrate. Start date support on Freedcamp Milestones (Business+ gated) maps to the milestone start date in Asana if present. Freedcamp Milestones that have no due date are flagged for the customer's review as Asana requires a due date for milestones to render in the project timeline.

Freedcamp Discussion threads are per-project threaded conversations with comments, timestamps, and author attribution. We migrate each Discussion as a new Comment on the corresponding task (the team identifies which task it maps to, or we create a stub task titled from the Discussion subject). Inline images in comments migrate as attachments to the Comment record. If no task mapping is provided, we create a Discussion-stub task per thread and attach all comments to it.

Freedcamp Calendar Events with a start and end time migrate to Asana Tasks with Start Date and Due Date set to the event window. Recurrence rules on Freedcamp events (Pro+ gated) are logged as a text field recurrence_description__c in Asana since Asana's native recurrence applies to Tasks, not Calendar Events. The event location migrates as a text field on the task. Calendar sharing and Google Calendar sync settings do not migrate and must be reconfigured in Asana.

Freedcamp Time Entries (built-in module on all plans) log duration, date, associated task or project, user, hourly rate, and billable flag. Asana has no native time-tracking field. We propose three options during scoping: (1) create a numeric custom field time_logged__c on tasks and sum entries per task, (2) use a dedicated time-tracking AppExchange tool (Harvest, Toggl, Everhour) post-migration, or (3) export to a CSV companion file for reference. The customer selects the strategy during scoping.

Freedcamp Wiki is a premium Business/Enterprise module with versioned pages and inline discussions. Asana Docs is the native knowledge-base equivalent but is a separate product tier. We migrate Wiki page titles and content as rich text into a designated Asana Project named for the Wiki, with each page as a task and the content in the task description. Version history migrates as a Comment on each page task. The customer must enable Asana Docs separately if they want a native knowledge-base experience.

Freedcamp Issue Tracker is a premium module with priority, status, type, assignee, reporter, due date, and custom fields. Asana has no native Issue Tracker equivalent. We propose two approaches: (1) create a dedicated Asana Project per tracker with tasks structured using priority and type Custom Fields, or (2) use a Jira Cloud AppExchange integration post-migration. We migrate all standard-issue fields; custom fields follow the standard template-reapplication process.

Freedcamp Invoices+ contains invoice and estimate records with line items, totals, client association, and status. Asana has no native invoicing capability. We export the Invoices+ records as a structured CSV including line items and totals, and flag this as requiring a dedicated billing tool (FreshBooks, QuickBooks Online, Wave, or an AppExchange invoicing app) post-migration. Invoice-client association migrates to the client name field in the destination tool.

Freedcamp CRM is a standalone module with Contact and Company records, pipeline stages, and deal tracking separate from the core project management data. Asana does not have a native CRM. We migrate CRM Contacts and Companies as Tasks in a designated CRM-migration Project, preserving name, email, phone, and any custom fields. Deals and pipeline stages are exported as CSV. A CRM replacement (HubSpot Free CRM, Pipedrive, or Salesforce Essentials) is recommended post-migration.

Files uploaded to Freedcamp Projects or Discussions migrate as Attachments to the corresponding Asana Project or Task. We replicate the folder structure as a list of tasks named for the folder hierarchy, with files attached to each folder task. Cloud storage integrations (Google Drive, Dropbox, OneDrive) on Pro+ tiers are preserved as link references in Asana. The file upload size limit in Asana is 100 MB per file on most plans, which exceeds Freedcamp's Free (10 MB), Pro (25 MB), Business (100 MB), and Enterprise (250 MB) limits.

Tags applied to Freedcamp Tasks, Projects, Issues, and other objects migrate as Asana Tags (workspace-level labels in Asana). Tag colors migrate where supported by the API. Tag association is preserved by adding the tag to the corresponding migrated task. Tags that apply to multiple object types in Freedcamp carry over as individual tag assignments in Asana.

Freedcamp User accounts (display name, email, role assignment) migrate to Asana Workspace members. We resolve by email match. Freedcamp role assignments (Group Administrator, Enterprise permission sets) are destination-side constructs and must be rebuilt in Asana Workspace settings post-migration. Inactive Freedcamp users are migrated as inactive Asana members at the customer's request.