Migrate from Freelo to Asana

Freelo Projects map 1:1 to Asana Projects. We export name, description, status (active/archived), start date, and deadline, and create matching Asana Projects in the destination workspace. Freelo project-level custom fields migrate as project-level custom fields in Asana (available on Starter and above). Archived projects in Freelo migrate as archived projects in Asana to preserve completion history.

Freelo To-Do Lists live inside Projects and group related Tasks. We map them to Asana Sections within the parent Project, preserving the original To-Do List name and ordering as the section order. If the destination workspace uses Asana's List view instead of Board view, To-Do Lists can alternatively map to a grouped task structure using a custom field or tagging convention. The customer chooses the target view during scoping.

Freelo Tasks map to Asana Tasks with title, description (migrated as rich text), assignee (resolved via user email lookup), due date, start date, priority, and status (completed/incomplete) preserved. Freelo task author maps to a custom text field task_author__c since Asana does not track task creation attribution natively. Completed tasks retain their completed_at timestamp as a custom date field completed_at__c.

Freelo Subtasks are a distinct nested object under Tasks. We migrate them as Asana Subtasks (Tasks with a parent_task gid). Parent linkage is preserved by resolving the Freelo parent task's migrated gid at insert time. Subtask assignee, due date, and completion status map identically to the parent task mapping. Subtasks without a valid parent in the migrated dataset are elevated to top-level Tasks and flagged for customer review.

Freelo user roster (Admin, Project Manager, Member roles) maps to Asana workspace members. We extract name, email, and display name from Freelo and match by email against the Asana destination workspace. Freelo Admin and Project Manager role distinctions do not have a direct Asana equivalent at the workspace level; they are preserved in a custom text field freelo_role__c for reference. The customer configures Asana project-level permissions and workspace membership after migration.

Freelo time entries (duration, cost value, currency) have no native Asana equivalent because Asana does not include a time-tracking object in its standard data model at any paid tier. We reconstruct time entries as custom fields on the relevant Task: a numeric custom field time_hours__c for logged duration and a text field time_cost__c for the calculated cost value and currency. If the customer licenses Asana Time Tracking (Advanced tier) post-migration, these custom fields can be migrated into that integration as a separate pass. We flag the reconstruction approach in the scoping document before migration begins.

Freelo file attachments up to 100 MB migrate as Asana Attachments (uploaded via the Asana Attachments API). Files between 100 MB and 250 MB require chunking or compression since Asana's API enforces a 100 MB limit on Starter and 250 MB on Advanced/Enterprise. Files exceeding 250 MB after compression are flagged for manual download-and-link handling. File captions and descriptions from Freelo migrate as attachment notes in Asana.

Freelo Comments attached to Tasks and To-Do Lists migrate as Asana Stories on the corresponding Task. Comment body (including any Markdown formatting) preserves as plain text, author maps to a text field comment_author__c (Asana Stories do not link to users outside the workspace membership), and timestamp migrates as created_at on the Story. Comment threading is not natively supported in Asana's task-level comments; flat comments migrate as sequential Stories.

Freelo custom fields on Tasks (text, number, date, dropdown types) export as name-value pairs via the Freelo API. We map them to Asana custom fields of the equivalent type during migration. Dropdown options are migrated as-is and must be verified against Asana's custom field option list (which Asana enforces strictly). Number and date fields migrate directly. Text fields migrate as text custom fields. The customer reviews the custom field mapping during scoping since Asana's custom field structure is global (workspace-level) rather than per-project in some configurations.

Freelo tags on Tasks are extracted as tag name arrays. If the destination Asana workspace uses the Tags feature (available on Starter and above), tags migrate directly as Asana Tags. If Tags are not enabled, they are mapped to a multi-select custom field freelo_tags__c. The customer selects the tag strategy during scoping.

If the Freelo Business module (paid tier) includes project status or health indicators, these migrate as Asana Project Status Updates. Status text, author, and timestamp map directly. If Freelo status data is not present (Free or Team plan), this object is skipped.

Freelo Notifications are ephemeral in-app and email alerts tied to user session state and do not constitute persistent project content. They are not migrated. The migration cutover includes disabling Freelo notifications at source to prevent post-migration alerts on stale data.