Migrate from Function Point to Microsoft Project

Function Point Projects map to Microsoft Project as the top-level container. Project metadata including name, status, start date, end date, and budget fields migrate directly. We preserve the budget threshold values as custom numeric fields in the destination because Microsoft Project tracks budget at the project level but not with the same threshold-alert model that Function Point uses for profitability visibility.

Function Point Jobs are the primary work-order unit and map to either Microsoft Project Tasks (for flat job structures) or Subprojects (for complex jobs with nested job-level task structures). We analyze the Job-to-Task ratio during scoping: if most Jobs have fewer than five child Tasks, we map Jobs to Tasks directly; if Jobs contain deep Task hierarchies, we map them as Subprojects for faithful WBS preservation. The decision is made per-project based on the customer's naming conventions and reporting needs.

Function Point Tasks live inside Jobs and map directly to Microsoft Project Tasks. Parent-child relationships to Jobs are resolved by inserting the Task under its parent Job-task row in the WBS. Custom task-status labels from Function Point are value-mapped to Microsoft Project Task Summary fields or text fields so that custom workflow states are preserved as readable data even if they do not map to native Task Status values.

Function Point Resources (team members and contractors) map to Microsoft Project Resources. The resource name, type (material vs work), and max units migrate. Hourly rates from Function Point's rate schedules are mapped to the Cost Rate Table in Microsoft Project on the Resources sheet. We extract the full rate table during scoping and apply per-user or per-role rates as a post-migration configuration step because Microsoft Project stores cost rates in a separate table rather than as a single field.

Function Point Timesheet entries (user, date, hours, Job/Task association, billable/non-billable flag) merge into Microsoft Project as Task Assignments with Actual Work and Actual Duration logged against the correct Task-Resource pair. We resolve the Function Point user to the matching Microsoft Project Resource by name or email lookup, then write the hours as assignment actuals. The billable/non-billable flag is stored as a custom flag field on the assignment since Microsoft Project does not have a native billable flag. Note: Microsoft Project does not have a native Timesheets module; timesheet reporting requires either the Resource Sheet view or a third-party add-in.

Function Point Companies have no native Microsoft Project object. We export the Company name, primary contact name, and contact email as a CSV during migration. The customer's admin maps these to SharePoint list entries, a Microsoft Dynamics 365 CRM, or a manual reference document. We do not attempt to store CRM data inside Microsoft Project because it does not support linked Contact or Account records.

Function Point Contacts (name, email, phone, title, Company association) have no Microsoft Project equivalent. We export Contacts to CSV with the parent Company linkage preserved. The customer maps these to a CRM (Microsoft Microsoft Dynamics 365 Sales , HubSpot, or another platform) as a post-migration step. Contact notes from Function Point Notes attached to Contacts are exported as free-text CSV records.

Function Point Estimates (line items with service names, quantities, rates, markups, and financial totals) have no Microsoft Project object. We export the full Estimate data — including line items, subtotals, and markup percentages — as a structured CSV mapped to a customer-provided budget tracking template (Excel, Smartsheet, or Power BI). We do not migrate Estimates as live records because Microsoft Project has no quote or estimate object; the financial data is delivered as a reconciliation document for the customer's finance team.

Function Point Invoices (line items, totals, payment status, client link, Posted vs Draft state) have no Microsoft Project equivalent. We separate Posted from Draft invoices during extraction. Posted invoices are exported as a billing history CSV with client name, invoice number, date, total, and status. Draft invoices are flagged as pending. The customer maps these to QuickBooks, Xero, or their accounting system as a separate billing-system handoff. We do not import Invoices into Microsoft Project because it has no invoice object.

Function Point Expenses (vendor, amount, date, description, Job/Project association) have no native Microsoft Project object. We export Expenses as a CSV with the Job and Project linkage preserved so that actual project costs can be reconciled against the budget fields in Microsoft Project. The customer maps these to their accounting system (QuickBooks, Xero) as a separate step.

Function Point Briefs hold project briefs and creative direction documents with unstructured content. We export Brief text as a CSV with the parent Project name and a character count. The customer chooses whether to paste Brief content into the Notes field on the corresponding Microsoft Project (Project Notes) or the leading Task (Task Notes). Long-form Brief content that exceeds the Notes field character limit is exported as a separate text file and linked by filename convention.