Migrate from Function Point to Jira

Function Point Projects map directly to Jira Software Projects. Each FP Project becomes a Jira project, preserving the project name, status (Active/On Hold/Complete), start and end dates as Jira Project dates, and budget fields as custom fields in Jira. If the FP Project has an On Hold status, we set the Jira project to archived or restrict access via permission scheme rather than deleting.

Function Point Jobs map to Jira Epics within the target Project. FP Job fields — job number, status, owner, cost codes, and description — map to Jira Epic fields. The Epic summary carries the Job name, and the Epic description carries the Job description. Parent-child linkage from Job to Project is preserved as the Epic-to-Project relationship. Jira Epic Link custom field connects child Stories (from FP Tasks) to the parent Epic.

Function Point Tasks map to Jira Stories, with the FP Task name as Story summary, description preserved, and status mapped through a value translation table. Custom Task labels in Function Point map to Jira labels or a custom field. If the FP Task has subtasks, these map to Jira Subtasks nested under the parent Story. Jira story points can be estimated if the team uses them; otherwise the FP estimated hours map to a custom field.

Timesheet entries (user, date, hours, Job/Task association, billable/non-billable flag) are among the most valuable historical records to migrate. Jira Software Premium ($18.30/user/month) has native time tracking with worklogs on issues. For Jira Standard, we create a custom field set on the Story: fp_timesheet_user (text), fp_timesheet_date (date), fp_timesheet_hours (number), fp_billable (checkbox). We link each timesheet entry to the Jira Issue derived from the parent FP Task or Job. Jira Premium customers can use the native worklog model instead.

Function Point Companies can map to Jira in two ways depending on your use case. For Jira Software customers who work with clients inside Jira, we create a Jira Project per client Company and link FP Company address and rep fields to project metadata. Alternatively, we create a custom field fp_client_name__c on the target Issues and populate it from FP Company, noting that Jira has no native CRM. FP Company phone, website, and address fields map to Jira project description or a Jira Issue custom field. We cannot retrieve FP Company custom fields via the API.

Function Point Contacts attach to Companies and carry name, email, phone, and role. In Jira, there is no Contact object. We map FP Contact to the Jira User (Assignee) where the FP Contact email matches a Jira user email. If no match exists, the Contact becomes a custom text field fp_contact_name__c or fp_contact_email__c on the Issue. FP Contact notes migrate as Jira Issue comments or a custom long-text field. We cannot retrieve FP Contact custom fields via the API.

Function Point Briefs hold project creative direction and scope documents as free-text content. Briefs export via CSV or API as unstructured text. We map Brief text to the Jira Issue description field of the Epic (FP Job) or a parent Story. If the Brief contains file attachments, we migrate them as Jira Issue attachments via the Jira API. The Brief-to-Jira mapping is content-dependent; long-form briefs may require chunking across multiple description updates or storage in Confluence as a linked document if Jira description length is exceeded.

Function Point Estimates contain line items with service names, quantities, rates, markups, and totals linked to Projects. Jira has no native Estimate or quote object. We preserve the FP Estimate as a Jira Story with a custom field set: fp_estimate_total__c (currency), fp_estimate_markup__c (number), and a description block listing the estimate line items as a text table. For agencies that need precise financial Estimates, we recommend maintaining a separate estimating tool (QuickBooks, Honey, or a spreadsheet) and linking the Jira Story to the estimate via a custom URL field. This is a known gap that requires workflow planning before migration.

Function Point Invoices (Draft and Posted) have no Jira equivalent. Jira Software is an issue-tracking tool, not a billing system. We do not migrate Invoices to Jira. For Draft invoices, we identify the count and total value during scoping and provide a manual-recovery spreadsheet: FP Invoice number, client, date, amount, and status for entry into your target billing system. For Posted invoices already synced to QuickBooks, we recommend verifying the QuickBooks sync is active and that no additional Invoice records need manual handoff. Function Point's IIF export can be used to push posted invoices directly to QuickBooks before or after migration.

Function Point Expenses (vendor, amount, date, description, Job/Project link) have no Jira equivalent. Jira Software does not support expense logging or vendor tracking. We flag all FP Expense records during scoping with a count and total spend. For teams that need to track project spend against Jira Stories, we can create a custom Jira field fp_expense_amount__c on the Issue and link it to the Jira Story derived from the parent Job, but this is a partial workaround for visibility only — it does not replace an expense management or accounts payable system.

Function Point maintains a service catalog (Service Groups containing Services with rates) used in Estimates. Jira has no native service catalog or product catalog for creative services. We export the FP service catalog as a spreadsheet during migration, noting service name, unit, rate, and markup. The customer uses this spreadsheet to configure products in a separate billing tool or to populate Jira custom fields on Stories where service-line visibility is required. This catalog export is delivered alongside the migration data package.

Function Point per-user and per-role rate schedules with markup percentages have no Jira equivalent. Jira does not model billing rates. We extract the full FP rate table during scoping and deliver it as a custom mapping spreadsheet for the customer's billing or finance team to configure in their target system (QuickBooks, Honey, or another estimating tool). The rate table export adds one to two business days to the migration timeline and is delivered before the Jira data import begins.

Function Point's REST API explicitly excludes custom fields on Companies and Contacts. Any custom fields created in Admin > System Set Up for these objects are not readable via the API. We cannot retrieve or migrate these values programmatically. During scoping, we identify every custom field on Companies and Contacts and provide a manual-recovery plan: we export the data via CSV from the FP Find Companies and Find Contacts pages, and we assist with manual entry into Jira custom fields post-migration. This is a high-severity limitation that requires customer participation and is flagged in the gotchas section.