Migrate from Float to Trello

Float Projects map to Trello Boards. The Project name becomes the Board name. Project status (active, archived) maps to Board archival state. Float's client association becomes a Board description field or a Trello Workspace label if the Business Class tier is used, since Trello does not have a native client-object hierarchy above Boards.

Float People records map to Trello Board Members. The person's name, email, and role transfer to the Trello member profile. We resolve People records by email against Trello member invitations and grant Board access during migration. Inactive Float users are migrated as inactive or excluded depending on the scoping decision; Trello's free tier limits member counts per Workspace which we check before migration.

Float Tasks map to Trello Cards within a Board. Task name becomes Card title, Task description becomes Card description, Task start and end dates become Card due dates, Task status maps to Card List position (To Do, In Progress, Done), and assigned hours are stored in the Card description as a formatted note since Trello has no native estimated-hours field.

Float's Schedule view (people allocated to tasks across a date range) has no native Trello equivalent. We extract the schedule as CSV and apply it as follows: scheduled hours per task are appended to the Card description as a formatted line, and task start and end dates become Card start and due dates using Trello's native date fields. Calendar-view scheduling cannot be replicated in Trello's Kanban model.

Float time entries (actual hours logged against tasks, available on Pro and above) have no Trello equivalent. Time entries are exported as a separate CSV report during migration and handed to the customer as a reference file. If the customer uses Trello's Time Tracking Power-Up post-migration, the CSV can be imported manually; this is outside standard migration scope.

Float Placeholders (unconfirmed hires or temp workers, tier-limited: 1 on Starter, 5 on Pro, unlimited on Enterprise) have no Trello equivalent. We flag all Placeholder records during scoping and present three options: exclude them from migration, convert them to standard People records (billing-active in Trello), or hold them for post-migration provisioning. The choice is made during discovery.

Float Departments group People and affect capacity rollup views. Trello has no native department concept. We map Departments to Trello Workspaces (separate Workspaces per department on Premium or Enterprise) or to a Label scheme within a single Workspace. Workspace mapping is chosen during scoping based on Trello tier and organizational complexity.

Float Roles categorize People (Developer, Designer, PM) and affect availability filtering. Trello has no native role concept. We store Role as a custom Label on the Board Member or as a text note in the member profile. If Trello Business Class is in use, custom fields on Cards can reference role-based labels for filtering.

Float Clients group Projects and appear in billing and reporting views. Trello does not have a native client object. We map Client name to a Board Label or to the Workspace name for single-client Boards. For multi-client organizations on Trello Premium or Enterprise, each Client maps to a separate Workspace for natural isolation of client-facing project data.

Float Custom Fields on People and Projects (discovered via paginated API before extraction) are mapped to Trello Labels for categorical fields and appended to Card or Board descriptions for text fields. Trello Business Class supports native custom fields on Cards which provides a closer semantic match. Standard Trello free and Standard tiers require custom field emulation via labels or description text. We enumerate all active custom fields during discovery and confirm the mapping strategy before migration.

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 and therefore has no corresponding source data to transfer.

Float Time Off blocks reduce a person's capacity for specific dates and affect scheduling views. Trello has no capacity or absence tracking. We export Time Off blocks as a separate CSV during migration. Post-migration, customers can use Trello's Calendar Power-Up or a third-party time-off tool to display availability. Capacity heatmap reporting is not available in Trello.