Migrate your Function Point data
Agency management platform combining project management, time tracking, resource scheduling, CRM, and billing for creative teams. Built for shops that need everything in one place but carry significant legacy data debt.
In its favor
Why people choose Function Point
The signal that keeps Function Point on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
The all-in-one consolidation appeals to agencies replacing three or more separate tools — project management, time tracking, and billing are native and tightly integrated rather than bolted on via third-party plugins.
Time tracking is frequently cited as Function Point's strongest feature, with users praising the accuracy of productivity hours recorded per Job and the transparency that gives project stakeholders.
Agencies with complex retainer and project-based billing models value the built-in financial layer, including budget tracking per Project and invoice generation linked directly to logged Timesheets.
The CRM module embedded in Function Point allows creative shops to manage client relationships without a separate CRM license, appealing to smaller agencies with constrained tool budgets.
Integration with QuickBooks for posted invoices and expenses provides a direct handoff to external accounting, reducing double-entry for agencies already using QuickBooks.
The user interface is consistently described as dated and slow, with reviewers reporting 30-second load times for single records and multi-step processes that require ten or more clicks to complete simple actions.
The mobile app functions only as a time-entry device — users cannot view comments, interact with Tasks, or manage Projects from the mobile experience, making it unsuitable for field or remote-heavy teams.
Onboarding new users is reported as difficult, with the tool's depth creating a steep learning curve that requires significant internal training investment before team members become productive.
Reporting flexibility is limited to pre-built templates; users who need custom analytics must export to CSV and build reports in external tools, which breaks the in-app workflow for power users.
Agencies growing past 20–30 users report that the platform's performance degrades under concurrent load, with multiple users sharing what reviewers describe as a 'slow-loading spreadsheet' experience.
Reasons to switch
Why people leave Function Point
The recurring reasons buyers give for replacing Function Point. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Function Point 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
Function Point pricing overview
Function Point publishes a Starter tier at $52 per user per month for teams of 5–9 users. Professional and Enterprise tiers are not publicly priced; prospective customers must contact sales for a quote. API access is gated behind Professional or Enterprise tiers and requires a CSM request to activate.
Starter
Tier 1 of 3
$52/user/month (5–9 users)
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Function Point's schedule — see our quote-based pricing →
What gets migrated
Function Point object support
Object-by-object support for Function Point migrations. Per-pair details surface during scoping.
Companies
Fully supportedStandard Companies module exports cleanly via CSV from the Find Companies page or via the REST API GET endpoint. We preserve all address, contact-rep, and billing fields as-is.
Contacts
Fully supportedContacts export via CSV or API and link to their parent Company via a foreign-key field. We maintain the linkage and preserve any Notes attached to each Contact.
Projects
Fully supportedProjects are the top-level container in Function Point's model. We export full project metadata including status, dates, and budget fields, then wire child Jobs and Tasks to the correct parent.
Jobs
Fully supportedJobs are the primary work-order unit. We extract Job details, assigned owner, status, and cost codes, and map them to Projects or Tasks in the destination based on the customer's naming conventions.
Tasks
Fully supportedTasks live inside Jobs and export via CSV or API. We preserve parent-child relationships to Jobs and handle any custom task-status labels as value-mapped fields.
Estimates
Mapping requiredEstimates link to Projects and contain line items with service names, quantities, rates, and markups. The financial subtotal and markup structure requires value-mapping to the destination's quote or estimate schema.
Timesheets
Fully supportedTimesheet entries export with user, date, hours, and Job/Task association. We preserve the billable/non-billable flag and the link to the rate schedule.
Expenses
Fully supportedExpenses are logged per Job or Project with vendor, amount, date, and description. We export all posted and unposted expense records and map them to the destination's expense or AP object.
Invoices
Mapping requiredInvoices export with line items, totals, payment status, and client link. We handle the distinction between Posted and Draft invoices carefully — Posted invoices map to completed billing records; Drafts are flagged as pending for manual review.
Briefs
Mapping requiredBriefs hold project briefs and creative direction documents. They export via CSV but store unstructured content that requires chunking and mapping to the destination's project or document object.
Notes
Mapping requiredNotes attach to Companies, Contacts, Projects, and Jobs as free-text entries. We export them as linked note records, but long-note content may require truncation or custom field handling in structured destinations.
Service Groups and Services
Mapping requiredFunction Point maintains a service catalog used in Estimates. We export Services and their associated Rates, then map them to the destination's product or service catalog.
Rates and Markups
Mapping requiredRate schedules define per-user or per-role billing rates. We export the full rate table and preserve markup percentages, mapping them to the destination's billing-rate or compensation objects.
Custom Fields (Companies and Contacts)
Not in this platformFunction Point's REST API explicitly states that custom fields created in Admin > System Set Up for Companies and Contacts are not accessible via any endpoint. We cannot read or write these values through the API. Any migration involving custom fields requires manual extraction from CSV export and manual entry at the destination.
| Object | Support | Notes |
|---|---|---|
| Companies | Fully supported | Standard Companies module exports cleanly via CSV from the Find Companies page or via the REST API GET endpoint. We preserve all address, contact-rep, and billing fields as-is. |
| Contacts | Fully supported | Contacts export via CSV or API and link to their parent Company via a foreign-key field. We maintain the linkage and preserve any Notes attached to each Contact. |
| Projects | Fully supported | Projects are the top-level container in Function Point's model. We export full project metadata including status, dates, and budget fields, then wire child Jobs and Tasks to the correct parent. |
| Jobs | Fully supported | Jobs are the primary work-order unit. We extract Job details, assigned owner, status, and cost codes, and map them to Projects or Tasks in the destination based on the customer's naming conventions. |
| Tasks | Fully supported | Tasks live inside Jobs and export via CSV or API. We preserve parent-child relationships to Jobs and handle any custom task-status labels as value-mapped fields. |
| Estimates | Mapping required | Estimates link to Projects and contain line items with service names, quantities, rates, and markups. The financial subtotal and markup structure requires value-mapping to the destination's quote or estimate schema. |
| Timesheets | Fully supported | Timesheet entries export with user, date, hours, and Job/Task association. We preserve the billable/non-billable flag and the link to the rate schedule. |
| Expenses | Fully supported | Expenses are logged per Job or Project with vendor, amount, date, and description. We export all posted and unposted expense records and map them to the destination's expense or AP object. |
| Invoices | Mapping required | Invoices export with line items, totals, payment status, and client link. We handle the distinction between Posted and Draft invoices carefully — Posted invoices map to completed billing records; Drafts are flagged as pending for manual review. |
| Briefs | Mapping required | Briefs hold project briefs and creative direction documents. They export via CSV but store unstructured content that requires chunking and mapping to the destination's project or document object. |
| Notes | Mapping required | Notes attach to Companies, Contacts, Projects, and Jobs as free-text entries. We export them as linked note records, but long-note content may require truncation or custom field handling in structured destinations. |
| Service Groups and Services | Mapping required | Function Point maintains a service catalog used in Estimates. We export Services and their associated Rates, then map them to the destination's product or service catalog. |
| Rates and Markups | Mapping required | Rate schedules define per-user or per-role billing rates. We export the full rate table and preserve markup percentages, mapping them to the destination's billing-rate or compensation objects. |
| Custom Fields (Companies and Contacts) | Not in this platform | Function Point's REST API explicitly states that custom fields created in Admin > System Set Up for Companies and Contacts are not accessible via any endpoint. We cannot read or write these values through the API. Any migration involving custom fields requires manual extraction from CSV export and manual entry at the destination. |
Gotchas
What to watch for in Function Point migrations
Issues we've hit on past Function Point migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Custom fields on Companies and Contacts are API-inaccessible
No API delete operations means relational cleanup must go through CSM
Invoice migration requires separating Posted from Draft records
API access requires an active CSM relationship and developer resources
Rate and markup schedules require custom mapping to destination billing models
| Severity | Issue |
|---|---|
| High | Custom fields on Companies and Contacts are API-inaccessible |
| Medium | No API delete operations means relational cleanup must go through CSM |
| Medium | Invoice migration requires separating Posted from Draft records |
| Low | API access requires an active CSM relationship and developer resources |
| Low | Rate and markup schedules require custom mapping to destination billing models |
Leaving Function Point?
Where Function Point customers move next
5 destinations Function Point can migrate to.
How a Function Point migration works
Four steps, Function Point-specific
Connect
Not publicly documented — requires CSM request to activate; developer credentials provisioned by Function Point support team into Function Point. Scopes limited to read-only on the data we move.
Map
We translate Function Point-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Function Point quirks before production.
Migrate
Full migration with Function Point rate-limit handling. Rollback available throughout.
FAQ
Function Point migration FAQ
Answers to the questions buyers ask most during Function Point migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Function Point 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 Function Point.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Function Point setup and destination — written quote back within a business day.