Migrate from Function Point to Asana

Function Point Companies map to Asana Organization members for internal team records and to Asana guest member profiles or Projects with a Company custom field for external client records. Address, billing contact, and account-manager fields migrate to Asana custom fields on the associated Project. If the Company has associated Contacts, those Contacts migrate as Asana members or guest profiles with the Company reference preserved in a custom field.

Function Point Contacts attach to a parent Company and map to Asana Organization members (if they are team users in Function Point) or guest profiles. We preserve the Contact's name, email, phone, and notes as Asana profile fields and custom text fields. Custom fields on Contacts are API-excluded per Function Point's documented design — we flag these during scoping and provide a manual-recovery CSV that the customer's admin enters manually post-migration.

Function Point Projects are the top-level container and map directly to Asana Projects. Project status, start date, end date, and budget fields migrate to Asana's Project due date, custom date fields, and a budget custom field. The Project's linked Companies become a custom multi-select or text field linking back to the client.

Function Point Jobs are the primary work-order unit carrying cost codes, budget thresholds, and financial status. We decompose Jobs into Asana Projects for standalone deliverables or Asana Sections within a parent Project for sub-work packages. Budget and cost-code fields from the Job migrate to Asana custom fields on the receiving Project or Section. A Job status field (Active, On Hold, Completed) maps to an Asana custom single-select field for tracking. Jobs linked to Estimates carry financial data that requires the Estimate to be processed first.

Function Point Tasks live inside Jobs and map directly to Asana Tasks. Parent Job association is preserved by placing the Task in the appropriate Asana Project or Section. Task status labels (custom in Function Point) map to Asana's custom single-select status field. Assignee, due date, and description migrate as-is. Notes attached to Tasks in Function Point migrate as Asana Task descriptions, with long notes chunked if they exceed Asana's description character limit.

Function Point Estimates contain line items with service names, quantities, rates, and markup percentages that do not map to a native Asana object. We extract the full Estimate and preserve it as a structured CSV alongside a set of Asana custom numeric fields on the Project (estimated hours, estimated total, markup percentage) that reference the Estimate value. The customer's billing team reviews the CSV post-migration. If the customer uses a billing add-on (for example, a cost-tracking Power-Up), we can map the Estimate line items to that tool's data model during migration.

Function Point Timesheet entries (user, date, hours, Job/Task association, billable/non-billable flag) map to Asana time tracking entries logged against the corresponding Task. We use the Asana API to create time entries with the original date and duration. The billable/non-billable flag from Function Point migrates to a custom single-select field on the Asana time entry. Per-user rate schedules are extracted separately and documented in a rate-table CSV for manual entry into Asana's billing configuration or a third-party add-on.

Function Point Expenses are logged per Job or Project with vendor, amount, date, description, and posted/unposted status. We export all Expenses as a structured CSV with Project, Job, vendor, amount, and status columns. For Asana Projects that have an associated expense-tracking add-on or integration, we map the expense records to that tool's data model. Without an add-on, Expenses do not have a native Asana representation and the CSV serves as the financial reconciliation document for the billing team.

Function Point Posted Invoices map to a completed billing status preserved in a custom field on the related Project. The invoice total, client, and payment status migrate to a billing custom field set. Asana has no native Invoice object, so Posted Invoice data is preserved as a CSV export with invoice number, client, total, status, and date. The customer's finance team reconciles this against their accounting system post-migration.

Function Point Draft Invoices cannot export to QuickBooks via IIF and similarly have no Asana equivalent. We flag Draft invoices during scoping, separate them from Posted records, and preserve them in a Draft-billing CSV with a pending-review flag. The customer reviews this list post-migration before finalizing or voiding the drafts in Function Point before cutting over to Asana.

Function Point Briefs hold project briefs and creative direction as unstructured content. We extract Brief text via CSV and map it to the Asana Project description field, with long briefs chunked into the Project description and additional Tasks created as Brief sections for sequential reading. If the Brief contains file attachments, those files migrate as Asana Project attachments (subject to the 100 MB file size limit per attachment).

Function Point maintains a service catalog (Service Groups containing Services with rates) used in Estimates. We export the full service catalog as a CSV and create corresponding Asana custom multi-select fields on Projects for service categorization. The rate table from the service catalog is included in the rate-table CSV for manual entry into Asana's billing configuration or a third-party tool.

Function Point per-user and per-role rate schedules with markup percentages do not map to any Asana native object. We extract the complete rate table (user, role, rate, markup percentage) as a structured CSV that the customer's admin reviews and enters into Asana custom fields, a billing add-on, or a spreadsheet for internal reference. This step adds one to two business days to the migration timeline and is completed before the Timesheet phase.

Function Point's REST API explicitly excludes custom fields created in Admin > System Set Up for Companies and Contacts. This is a documented design exclusion, not a temporary limitation. We cannot retrieve these values through any endpoint. During scoping, we identify every custom field on these objects, export the data via CSV from Function Point's module Find page, and provide a manual-recovery plan: the customer enters the values into Asana custom fields on the relevant Projects or member profiles post-migration.