Migrate from Float to Microsoft Project

Float Projects map to Microsoft Project project files (MPP) or Project Online projects. We extract Project name, status (active, archived), client association, and start/end dates from Float and map them to the project-level fields in Microsoft Project. The client association from Float's client grouping maps to an Enterprise Project Outline Code or a custom Client field in Microsoft Project.

Float People records map to Microsoft Project named Resources with Max Units (typically 100% for full-time, lower for part-time), cost rate, and bill rate from Float's cost_rate and bill_rate fields. The resource type (Work, Material, or Cost) is set to Work for team members. We resolve inactive Float People to inactive Resources with Max Units at 0% to preserve the record for historical reporting without counting against Microsoft Project licensing.

Float Tasks map to Microsoft Project task rows. Float's assigned hours and date range become Microsoft Project Start and Finish dates with Duration calculated from the date span. Float's task name, estimated hours, and task notes migrate directly. Float's has no dependency field, so tasks import as independent — we deliver a predecessor mapping document listing inferred Finish-to-Start relationships based on sequential task order or sub-project structure for manual creation post-migration.

Float's Schedule view (the core resource allocation data) is the migration's most complex mapping. We export the schedule as a CSV including team member, date range, task, project, client, and scheduled hours. Each row maps to a Microsoft Project Task Assignment: the resource (from People), the task (from Task), and the scheduled hours become Assignment Units or Work values. For part-time allocations (less than 8 hours/day), we set the Assignment Units to the fractional value.

Float Placeholders (unconfirmed hires or future headcount) have no native Microsoft Project equivalent. We offer two strategies: convert Placeholders to Generic Resources with Max Units matching the placeholder allocation, or exclude Placeholders from migration with a written inventory of all Placeholder records (person name, role, project, date range, hours) for manual Resource creation post-migration. The strategy is chosen during scoping based on the customer's resource-pool policy and Float plan tier.

Float Departments map to Microsoft Project Resource Groups. The department name and its relationship to assigned People transfer as the Resource Group field on each Resource record. Resource Group enables filtering and resource leveling views by department in Microsoft Project.

Float Roles (e.g., Developer, Designer) categorize People for availability filtering. Microsoft Project Resources do not have a native Role field. We map Float Roles to a custom Resource text field (e.g., Role__c) or use the Resource Initials field as a shorthand. The customer selects the preferred approach during scoping.

Float Clients group Projects and appear in billing and reporting views. Microsoft Project has no native Client object — Projects are standalone. We map Float Client names to a custom Project-level text field (e.g., Client__c) or an Enterprise Project Outline Code if the customer uses Project Online and has Enterprise Custom Fields configured.

Float time entries (actual hours logged against Tasks) on Pro and above plans map to Microsoft Project task-level Actual Work entries. We match Float time entries to Microsoft Project tasks by task name and date, then write the logged hours as Actual Work on the corresponding assignment row. Planned hours from Float migrate as Work or Baseline Work depending on the destination tier. Historical time entries spanning billing periods are flagged for fiscal period alignment in Microsoft Project before import.

Float Time Off blocks represent capacity reductions for specific dates. Microsoft Project has no native Time Off object, but Time Off blocks can be represented as generic task rows with no work (zero hours) or as resource-specific availability notes in a custom field. We deliver Time Off as a written calendar inventory with person, start date, end date, and type (vacation, sick, leave) for manual entry or Power Automate workflow recreation post-migration.

Float custom fields on People vary per account and require pre-migration schema discovery via the custom-fields API endpoint. We enumerate all active custom fields, types (text, number, dropdown), and options before migration. Text custom fields map to Microsoft Project custom Resource text fields; number fields map to number custom fields; dropdown fields map to custom fields with picklist options where supported. Project Online Enterprise Custom Fields must be configured in the admin settings before migration begins.

Float custom fields on Projects migrate to Microsoft Project custom Project-level fields. We apply the same type-mapping logic used for People custom fields: text to text, number to number, dropdown to picklist. The destination Project Online tenant must have the Enterprise Custom Fields feature enabled and the fields pre-created in the PWA settings before we begin the project import phase.