Migrate from Float to monday Work Management

Float Projects map directly to monday.com Boards. Each Float Project becomes a monday.com Board with the Project name, client association preserved as a Board label or Groups-by structure, and project status mapped to an active/archived Board state. We create Boards in the appropriate Workspace during migration. Projects with high task counts may be split into multiple monday.com Boards if the customer prefers granular board management.

Float People records map to monday.com Team Members. We preserve name, email, role, department, cost rate, and bill rate as User profile fields and Custom Columns. Float's active-user billing model means some People records may be inactive or placeholder-adjacent; we flag these for the customer's admin to set as inactive monday.com users or exclude from the seat count during migration scoping.

Float Tasks map to monday.com Items within the corresponding Board. Task name, start date, end date, assigned hours, and assignee migrate as standard columns (Name, Date, Number, Person). Task status in Float maps to a monday.com Status column with values aligned to the original Float stages. Task priority and tags migrate as Labels or Dropdown columns.

Float Placeholders represent unconfirmed hires or temporary workers. monday.com has no native Placeholder object. We flag all Placeholder records during scoping, identify them as a separate dataset, and recommend the customer either create them as inactive monday.com Users pending confirmation or maintain a separate tracking document. Placeholder-heavy datasets require a migration inventory step where each Placeholder is mapped to a named owner or marked for exclusion.

Float Departments group People and affect capacity rollup views. monday.com does not have a native Department object, but Teams (Enterprise) or Groups within Boards can approximate the grouping. We recommend using monday.com Teams at Enterprise tier for org-wide department separation, or Board-level Groups for project-scoped department representation. The customer chooses the grouping strategy during scoping.

Float Roles categorize People (Developer, Designer, Project Manager) and affect availability filtering in scheduling views. We map Role to a monday.com Text or Dropdown column on the People Board, preserving the original role names for scheduling constraint reference. Role filtering requires a manual monday.com Workload view configuration post-migration.

Float Clients group Projects and appear in billing and reporting views. monday.com has an optional native Clients feature (separate product) or Clients can be stored as a Company name column on Boards. We map Client names to a Text or Dropdown column on the Project Board for reporting grouping. Clients with billing relationships may require the monday.com Clients integration as a separate setup.

Float Time Entries record actual hours logged against Tasks with date, person, and hours. monday.com's native time tracking requires a Pro plan ($19/seat/month) and maps to a Time Tracking column linked to Items. We migrate time entries as historical Time Tracking entries on the corresponding Items. Basic and Standard monday.com accounts do not have native time tracking; entries migrate as read-only Number columns with notes field documenting the historical data.

Float Time Off blocks capacity for People on specific dates. monday.com has no native Time Off object. We migrate Time Off as Date range columns on the People Board with a Time Off label, or flag it for a separate Calendar integration setup. Capacity planning based on Time Off requires the monday.com Workload view (Pro) or a manual review of the People Board post-migration.

Float Custom Fields on People and Projects use a paginated API with created_at filtering. We discover the full custom field schema before extraction, enumerating all active custom fields, types, and option lists. Custom field types (text, number, date, person, dropdown) map to equivalent monday.com column types. Some Float custom field types have no monday.com equivalent (e.g., complex formula fields); these are flagged for manual rebuild or conversion to a Text column with original values preserved.

Float's Schedule view exports as CSV including team, date range, task, project, client, and scheduled hours. For large schedules spanning more than the export window, we chunk into weekly or bi-weekly CSV exports, deduplicate on task ID and date, and reassemble before loading into monday.com. Schedule rows map to Items with Timeline (Start Date + End Date) and Person columns populated from the export.

Float does not have a native Milestone object. Projects have end dates but no milestone sub-objects. We do not migrate milestones since the concept does not exist in Float's schema. If the customer has documented milestones externally, they can be added as Date-type Items or Timeline milestones in monday.com post-migration.