Migrate your Float data
Visual resource scheduling and capacity planning tool for professional services teams. Connects people allocation to project profitability with a clean calendar-first UX.
In its favor
Why people choose Float
The signal that keeps Float on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Clean, visual schedule interface makes assigning people to projects fast and reduces friction compared to spreadsheet-based capacity planning.
Billing model charges only active scheduled users, so teams pay for capacity they actually use rather than total headcount.
Built-in time tracking on Pro and above plans eliminates the need for a separate timesheet tool for most professional services teams.
Strong resource planning focus with capacity heatmaps and utilization views helps managers balance workloads across projects.
Purpose-built for agencies and professional services with native client grouping and project margin tracking.
Teams outgrow the limited project management features — no Gantt charts, weak dependency management, and reporting feels shallow for complex portfolios.
Difficulty managing part-time staff, freelancers, and syncing Float data with external payroll or leave systems creates double-entry work.
As teams scale past 100 people, the lack of advanced customization and bulk editing makes ongoing maintenance tedious.
Reporting and analytics lag behind dedicated business intelligence tools, leaving teams exporting to spreadsheets for real insights.
The platform lacks native budget tracking and financial integration, forcing finance teams to maintain parallel spreadsheets.
Reasons to switch
Why people leave Float
The recurring reasons buyers give for replacing Float. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Float fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Float pricing overview
Float uses per-active-user monthly billing — only people who are actually scheduled count toward the bill, not total users in the account. Both monthly and annual billing are available, with a 30-day free trial on the Pro plan without requiring a credit card. The three tiers align to team sizes: Starter for 50–100 people, Pro for 100–300, Enterprise for 300+.
Starter
Tier 1 of 3
$7/person/month
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Float's schedule — see our quote-based pricing →
What gets migrated
Float object support
Object-by-object support for Float migrations. Per-pair details surface during scoping.
Projects
Fully supportedProjects are the top-level container in Float, grouping Tasks under a client. We migrate Projects with their metadata (name, status, client association) and map client-linked projects to the destination's equivalent grouping structure.
People
Fully supportedPeople are the team member records in Float. We preserve name, role, department, cost rate, and bill rate. We handle inactive users carefully since billing counts only active scheduled users.
Tasks
Fully supportedTasks belong to Projects and can have assigned hours, start/end dates, and assignee. We migrate Tasks with their scheduling data and preserve hour estimates against actuals where present.
Placeholders
Mapping requiredPlaceholders represent unconfirmed or future hires. Starter allows 1, Pro allows 5, Enterprise unlimited. We flag Placeholders during migration scoping — most destination systems lack an equivalent concept and require a decision on whether to import as real People records or exclude.
Departments
Fully supportedDepartments group People and affect capacity rollup views. We migrate department structure and preserve the relationship to assigned People.
Roles
Fully supportedRoles categorize People (e.g., Developer, Designer) and affect availability filtering. We preserve Role names and assignments to maintain scheduling constraint logic in the destination.
Clients
Fully supportedClients group Projects and appear in Float's billing and reporting views. We migrate Client names and associations to Projects. Some destination systems conflate Clients with Companies/Accounts and require a mapping step.
Time Entries
Fully supportedTime Entries record actual hours logged against Tasks. Pro and above track planned hours vs actuals. We migrate time entry history with task association, date, and hours. The billing period alignment must be confirmed to avoid splitting entries across reporting periods.
Time Off
Fully supportedTime Off records block capacity for People on specific dates. We migrate time off blocks and preserve the person's capacity reduction during the affected date range.
Custom Fields
Mapping requiredFloat supports custom fields on People and Projects. Custom fields use a paginated API with created_at filtering. We discover the full custom field schema before migration and map field types (text, number, date, choices) to the destination's equivalent. Choice fields with specific option sets require explicit value mapping.
Schedules
Fully supportedThe Schedule view shows People allocated to Tasks across a date range. We export the schedule as CSV including team, date range, task, project, client, and scheduled hours. For large schedules we paginate through the date range to avoid truncation.
Milestones
Not in this platformFloat does not have a native Milestone object. Projects can have end dates but no milestone sub-objects. We do not migrate milestones since the concept does not exist in Float's schema.
| Object | Support | Notes |
|---|---|---|
| Projects | Fully supported | Projects are the top-level container in Float, grouping Tasks under a client. We migrate Projects with their metadata (name, status, client association) and map client-linked projects to the destination's equivalent grouping structure. |
| People | Fully supported | People are the team member records in Float. We preserve name, role, department, cost rate, and bill rate. We handle inactive users carefully since billing counts only active scheduled users. |
| Tasks | Fully supported | Tasks belong to Projects and can have assigned hours, start/end dates, and assignee. We migrate Tasks with their scheduling data and preserve hour estimates against actuals where present. |
| Placeholders | Mapping required | Placeholders represent unconfirmed or future hires. Starter allows 1, Pro allows 5, Enterprise unlimited. We flag Placeholders during migration scoping — most destination systems lack an equivalent concept and require a decision on whether to import as real People records or exclude. |
| Departments | Fully supported | Departments group People and affect capacity rollup views. We migrate department structure and preserve the relationship to assigned People. |
| Roles | Fully supported | Roles categorize People (e.g., Developer, Designer) and affect availability filtering. We preserve Role names and assignments to maintain scheduling constraint logic in the destination. |
| Clients | Fully supported | Clients group Projects and appear in Float's billing and reporting views. We migrate Client names and associations to Projects. Some destination systems conflate Clients with Companies/Accounts and require a mapping step. |
| Time Entries | Fully supported | Time Entries record actual hours logged against Tasks. Pro and above track planned hours vs actuals. We migrate time entry history with task association, date, and hours. The billing period alignment must be confirmed to avoid splitting entries across reporting periods. |
| Time Off | Fully supported | Time Off records block capacity for People on specific dates. We migrate time off blocks and preserve the person's capacity reduction during the affected date range. |
| Custom Fields | Mapping required | Float supports custom fields on People and Projects. Custom fields use a paginated API with created_at filtering. We discover the full custom field schema before migration and map field types (text, number, date, choices) to the destination's equivalent. Choice fields with specific option sets require explicit value mapping. |
| Schedules | Fully supported | The Schedule view shows People allocated to Tasks across a date range. We export the schedule as CSV including team, date range, task, project, client, and scheduled hours. For large schedules we paginate through the date range to avoid truncation. |
| Milestones | Not in this platform | Float does not have a native Milestone object. Projects can have end dates but no milestone sub-objects. We do not migrate milestones since the concept does not exist in Float's schema. |
Gotchas
What to watch for in Float migrations
Issues we've hit on past Float migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Placeholder limits by tier block full import
Active-user billing model affects migration scoping
Schedule CSV export truncates at date-range boundaries
Custom fields require pre-migration schema discovery
Time entry history spans billing periods
| Severity | Issue |
|---|---|
| Medium | Placeholder limits by tier block full import |
| High | Active-user billing model affects migration scoping |
| Medium | Schedule CSV export truncates at date-range boundaries |
| Low | Custom fields require pre-migration schema discovery |
| Medium | Time entry history spans billing periods |
Leaving Float?
Where Float customers move next
5 destinations Float can migrate to.
How a Float migration works
Four steps, Float-specific
Connect
Bearer token into Float. Scopes limited to read-only on the data we move.
Map
We translate Float-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Float quirks before production.
Migrate
Full migration with Float rate-limit handling. Rollback available throughout.
FAQ
Float migration FAQ
Answers to the questions buyers ask most during Float migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Float migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther project management tools we support
Ready when you are
Migrate Float.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Float setup and destination — written quote back within a business day.