Migrate from Freelo to Microsoft Project

Each Freelo Project maps directly to a single Microsoft Project plan (.mpp file for Project Desktop, or a Project Web App project plan for Project Online). Project name, description, start date (inferred from earliest task if not explicit), and deadline (mapped to project Finish date) migrate as-is. The Freelo project's status (active, archived) maps to Project Desktop's percent complete field or Project Online's Project Finish Date. If the customer has multiple Freelo projects that logically belong in one Microsoft Project plan, we offer a merge during scoping.

Freelo To-Do Lists map to Microsoft Project Summary Tasks at the Phase or stage level of the WBS. The To-Do List name becomes the Summary Task name; its description maps to the Summary Task's Notes field. Outline Number is assigned based on the To-Do List's position within the project. The To-Do List's creation date and manager assignment are preserved as custom fields or Notes. We confirm during scoping whether each Freelo To-Do List should generate a new Summary Task or whether the customer wants a flattened task list with custom columns instead.

Freelo Tasks map directly to Microsoft Project Tasks. We map title, description (to the Task Name and Notes), deadline (to Finish date), assignee (to a Resource assignment on the task), author, creation date, completion date, and status. If the task has no explicit start date in Freelo, we infer it from the project start date or from the deadline minus estimated duration. Freelo task priority (low, medium, high) maps to a custom Priority field in Microsoft Project since the built-in Priority field uses a 1-10 numeric scale.

Freelo Subtasks nested under a Task map to child Tasks in the Microsoft Project WBS outline, inheriting the parent's Summary Task structure. Parent-child linkage is preserved as Outline Level (indented under the parent Task). We retain the Freelo subtask name, status, assignee, and deadline. If a Freelo task has multiple Subtasks with conflicting assignees, we create individual resource assignments on the child tasks rather than on the parent. Outline numbers are assigned sequentially during import.

Freelo users (Admin, Project Manager, Member roles) map to Microsoft Project Resources in the Resource Sheet. We export each user's name, email, and role. During migration, we create Resource records in the destination .mpp file with the user's name as the Resource Name. If the customer uses Microsoft Project Online or Project for the web, we can map Freelo users to existing Microsoft 365 users by email for resource booking. Role information is preserved in a custom Resource Notes field. Any Freelo user without a match in the destination is flagged in the reconciliation report.

Freelo time entries (duration and cost value per task) map to Microsoft Project's Duration and Work fields on the relevant task. If the customer has set resource cost rates in the Resource Sheet, Microsoft Project automatically calculates total task cost. We map the time entry currency and cost value from Freelo to a custom cost field or to the standard Cost field in the destination. This mapping requires confirmation during scoping because Freelo's cost tracking is only available on paid tiers and some teams use it for billing rather than project planning.

Freelo file attachments (up to 100 MB per file) are exported from the ZIP bundle. We re-upload them as attachments on the relevant task. In Microsoft Project Desktop, files can be attached to tasks via the Task Inspector or inserted as objects; larger files are linked rather than embedded to keep the .mpp file size manageable. If the destination is Project Online or Project for the web integrated with SharePoint, we attach files directly to the SharePoint document library associated with the plan. Files exceeding 50 MB per Microsoft Project's attachment limit are flagged for manual review.

Freelo comment threads on Tasks and To-Do Lists have no native Microsoft Project equivalent. Task Notes is a single text field per task, not a thread. We migrate the most recent or most relevant comment to the Task Notes field. If the customer needs full comment history preserved, we create a SharePoint document library as a companion to the migrated plan, with one text file per task containing the comment thread. This is decided during scoping; the default is Notes field migration only.

Freelo custom fields on Tasks (text, number, date, dropdown) are exported as name-value pairs from the API. We create matching custom fields in Microsoft Project (Text1-30, Number1-10, Date1-10, Flag1-10 depending on type) and populate them during migration. Dropdown values in Freelo become valid custom field values in Microsoft Project's custom field picklist. We present all custom fields for customer review during the mapping phase because Freelo does not expose field type schema descriptors in the API response.

Freelo notifications (in-app alerts, email cadence, weekly reports) are ephemeral session-state data and are not migrated. The activity log (state-change history per task) is not a persistent project record in Freelo and has no Microsoft Project equivalent. We do not migrate these objects. If the customer needs an audit trail of past task changes, Freelo's activity log export can be provided as a separate CSV for manual reference outside the project plan.