Migrate from Freelo to monday Work Management

Freelo Projects map 1:1 to monday.com Workspaces, with a primary Board created inside each Workspace to hold the migrated content. We preserve project name, status (active/archived), description, start date, and deadline as Workspace-level metadata. If Freelo's project has a custom domain or logo, we note it as a manual configuration item in monday.com. Workspace visibility settings default to private during migration and are documented for the customer to configure share settings post-migration.

Freelo To-Do Lists map to monday.com Groups within the target Board. We preserve the ordering of To-Do Lists as Group position values so that the original left-to-right or top-to-bottom sequence is maintained in the destination. Each Group receives the To-Do List's name, description, and status. Group color coding from Freelo is not a native monday.com attribute; we document it for manual styling if the customer uses monday.com's color customization per Group.

Freelo Tasks map directly to monday.com Items. The title maps to Item name, description to the Text Column, deadline to the Date Column, assignee to the People Column (resolved by email against monday.com User accounts), and status to the Status Column. Freelo's task priority (low/medium/high) maps to a Label Column or a dedicated Priority dropdown column depending on the customer's preference during scoping. The original Freelo task author is preserved in a Text Column as a read-only reference.

Freelo Subtasks are a distinct nested object under Tasks. In monday.com, Sub-items live as children of their parent Item within the same Board. We preserve the parent-child linkage by setting subitem_parent_item_id during import and keeping the original Subtask title, assignee, deadline, and status. Freelo Subtask ordering is preserved as subitem position within the parent. If the source Freelo account has Subtasks on the Business tier, we confirm sub-item billing implications in monday.com because sub-items count toward item limits on lower tiers.

Freelo user accounts (Admin, Project Manager, Member roles) map to monday.com User records by email address. We export name, email, and role for each user. monday.com assigns permissions at the Workspace and Board level rather than per-role labels, so we create a Workspace invitation for each user and assign them the closest equivalent role (Workspace Admin, Member, or Viewer). Freelo user preferences and out-of-office settings are not migrated because they are account-level data.

Freelo time entries (duration, cost value, currency) map to monday.com's native Time Tracking Column if the destination account is on Pro ($19/seat) or above. On Standard ($12/seat), we fall back to a Numbers Column to hold the logged duration and a separate Numbers Column for the cost value. We flag this decision during scoping based on the customer's chosen monday.com plan. Currency fields migrate as-is; currency conversion is out of scope.

Freelo file attachments migrate to monday.com File Columns. Files under 100 MB are re-uploaded directly via the monday.com API. Files at or above 100 MB are split into chunks below the threshold before upload; files that cannot be cleanly split are flagged for manual handling and documented in the migration report. We preserve file captions and uploader attribution as a Text Column beside each File Column entry. The 500 MB free-tier storage limit on Freelo is checked during scoping to confirm all files fit within the destination's storage allocation on the selected plan.

Freelo Comments attached to Tasks or To-Do Lists migrate to monday.com Item Updates (the comment stream on each Item). The comment body, author name, and timestamp transfer directly; Markdown formatting in Freelo comments is preserved as-is. Comment threading depth in Freelo maps to a flat comment list in monday.com since monday.com does not support nested replies within Items. Any embedded file references in comments are resolved by cross-referencing the Freelo file UUID against the attachment export.

Freelo custom fields on Tasks (text, number, date, dropdown) map to monday.com Column types that match their data type. Dropdown values migrate as Label or Status column options; number fields migrate as Numbers Column; date fields migrate as Date Column; text fields migrate as Text Column. Freelo's API returns custom field values without a typed schema descriptor, so we infer type from the value format during the export pass and present the mapping for customer review before import. Any custom field that cannot be typed unambiguously is migrated as a Text Column with the original value preserved.

Freelo notifications are ephemeral in-app or email alerts tied to user session state and activity. They do not constitute persistent project content and are not migrated. We document the notification rules active on each Project during scoping so the customer can rebuild equivalent notification triggers in monday.com's automation builder post-migration.

Freelo's activity log tracks project state changes over time but is not a persistent business record suitable for migration. monday.com's own activity log is rebuilt automatically as users interact with Items post-migration. Historical activity log records from Freelo are not transferred.

Freelo's Business module includes invoicing and advanced billing features that exist only on paid tiers. These records do not have a native equivalent in monday.com's work management product (which does not include billing). We export invoice metadata as a CSV for the customer's records but do not create corresponding monday.com objects. If the customer needs billing capabilities, that is a separate tool decision post-migration.