Migrate from Freedcamp to Microsoft Project

Freedcamp Projects map directly to Microsoft Project plans. Project title, description, status (active/archived), and creation date transfer to Project Name, Summary Task notes, and Project Summary fields. Freedcamp's Project-level Custom Fields (Enterprise-only) are exported as a template schema CSV and flagged for manual reapplication in Microsoft Project because Project uses a different custom field data model. The Freedcamp Project owner maps to the Project Manager field in Project.

Freedcamp Tasks map to Microsoft Project tasks. Title, description, assigned user, due date, start date, priority, and status transfer. Freedcamp's Open/In Progress/Resolved/Closed status values map to Project's Not Started/In Progress/Completed state fields. Tasks without dependencies in Freedcamp will import as independent Project tasks requiring manual dependency wiring if the customer requires linked scheduling. Freedcamp subtasks become Summary Tasks with indented subordinate tasks in Project.

Freedcamp Milestones map to Microsoft Project tasks with the Milestone flag set to Yes. Milestone title, due date, description, and completion status transfer. Freedcamp Milestones are standalone deadline markers and become zero-duration milestone tasks in Project. Freedcamp's Start Date for milestones requires Business or Enterprise; we flag any milestone without a start date and default it to the due date minus one day for Project compatibility.

Task Custom Fields from Freedcamp Business and Enterprise plans (text, input, date, number, checkbox, drop-down types) export with their values per task and their template schema separately. We map drop-down options to Project's Outline Code or custom picklist fields where Project supports them. Text, date, and number types map to Project custom text, date, and number fields. We preserve a companion CSV with the full Freedcamp template schema including separators and required flags for the customer to reapply manually in Project.

Project-level Custom Fields require Freedcamp Enterprise and the Project Overview app. Microsoft Project stores project-level attributes differently (as Summary Task fields or project-level custom fields in Project Online). We export the Enterprise-plan project custom field schema separately, preserve all values in a companion CSV, and document the recommended manual reapplication process. This data is not lost but requires manual action in the destination.

Freedcamp's built-in Time tracking module maps to Project task assignment data. Duration, date, associated task, user, and billable flag transfer. For Project Online, time entries map to time-phased assignment data on the task. For desktop MPP files, we provide a Time Entries companion CSV because Project Desktop does not natively support time-phased data in the same way. Hourly rates and notes export with the entry for reference.

Freedcamp Discussion boards are per-project threaded conversations with timestamps and author attribution. Microsoft Project has no native discussion or comment feature in the desktop product; Project Online supports SharePoint-integrated comments if the project plan is stored in SharePoint. We export all discussion threads as a structured CSV (Project Name, Discussion Title, Comment Author, Comment Body, Timestamp) for the customer to archive in SharePoint, Teams, or a document library.

Files uploaded to Freedcamp Projects or Discussions export as binary blobs with folder structure, name, size, upload date, and uploader metadata. For Project Online, files attach to the SharePoint document library associated with the project plan. For desktop MPP files, we provide a structured file manifest CSV and recommend archiving files in a shared OneDrive or SharePoint location. Freedcamp's cloud storage integrations (Google Drive, Dropbox, OneDrive) require reconnection in the Microsoft ecosystem.

Freedcamp Calendar Events map to Microsoft Project tasks with start/end dates. Event title, start datetime, end datetime, recurrence rules, and associated project transfer. Recurring event patterns from Freedcamp become recurring tasks in Project where Project supports recurrence. Freedcamp's Google Calendar sync setting does not transfer and must be reconfigured in Microsoft Outlook integration separately.

Freedcamp Tags applied to Tasks, Projects, and other objects migrate as semicolon-delimited strings in a companion text field. Microsoft Project does not have a native tag or label object. We recommend the customer apply Project categories or keywords after migration, or use a companion CSV to drive bulk categorization through Power Automate.

Freedcamp Issue Tracker (Business/Enterprise premium module) maps to Project tasks with an Issue flag. Priority, status, type, assignee, reporter, due date, and custom fields transfer. Issue-specific attributes (issue type, reporter) export as text fields or custom fields on the task. The Issue Tracker module does not exist as a standalone object in Microsoft Project, so all issues become tasks within the project plan with a type marker to distinguish them from standard work tasks.

Freedcamp Wiki pages (Pro plan and above) contain rich content with version history metadata and inline discussions. Microsoft Project has no native wiki or knowledge-base feature. We export all wiki content as structured HTML files and provide a page inventory with the original wiki structure, so the customer can archive the content in SharePoint, Confluence, or a document library. Wiki page associations to projects map to the nearest Project name for context.