Migrate from Function Point to Trello

Function Point Projects map directly to Trello Boards. Project name becomes the Board name, Project status (Active/On Hold/Complete) maps to archiving or board closure, and project dates migrate as optional due dates on Lists or as Board description. One Project equals one Board; the two-system architecture is a 1:1 relationship at this level.

Function Point Jobs map to Trello Lists within the parent Board (Project). Each Job becomes a List with the Job name as the List title. Job status (Active/On Hold/Complete) maps to List archiving or card movement. Jobs that represent distinct work phases or deliverables map cleanly to the column structure Trello expects, but deeply nested sub-Jobs require a subcard strategy or a flat list with label prefixes.

Function Point Tasks map to Trello Cards within the parent List (Job). Task name becomes the Card title, Task status maps to Card movement between Lists or archiving, and Task due dates migrate as Card due dates. Task assignees map to Card Members. Long task descriptions are migrated as Card descriptions. Custom task-status labels are mapped as Trello Labels with consistent color coding across the Board.

Function Point Timesheets represent billable hours logged per user per Job. Trello has no native time tracking as a core feature. We extract Timesheet entries by user, date, hours, and Job association, then map them as Trello Custom Fields (Number type, available on Standard and above) on each Card, or as a separate reference spreadsheet linked to the Card via description. The billable/non-billable flag is preserved as a Label or a Checkbox field. Customers who need native time tracking should activate a Trello Power-Up like Clockify or Planyway post-migration.

Function Point Estimates contain line items with service names, quantities, rates, and markup percentages. Trello has no native estimate or quote object. We extract Estimates as structured data and create a Trello Card Checklist titled 'Estimate Summary' with line items as checklist items, or we store the estimate total as a Number Custom Field on the Card. Markup structure cannot be preserved natively in Trello; the full rate table is documented in the manual-recovery workbook for the customer's admin to cross-reference.

Function Point Expenses are logged per Job or Project with vendor, amount, date, and description. Trello has no native expense tracking. We extract all Expense records and map them to the corresponding Card (Project or Job) as a Card description entry, or as a separate CSV export linked in the Card. Posted versus Draft expense status is preserved in the CSV and documented for the customer's billing team to reconcile in QuickBooks or their accounting tool.

Function Point Invoices track billing records linked to Jobs with line items, totals, and payment status. Trello has no native invoicing. We separate Posted from Draft invoices during scoping (Function Point's API exports these differently). Posted invoices are exported as a CSV with all line item detail and linked to the corresponding Trello Card by Job. Draft invoices are flagged as unconfirmed and documented for billing-team review. Invoiced amounts and payment status cannot be tracked inside Trello post-migration without a Power-Up integration.

Function Point Companies represent clients with address, billing, and contact-rep data. Trello has no native Company or Account object. We extract Companies as Board Members in the Trello workspace (with the company name as the display name) and preserve the company address and primary contact in the Card description of relevant Cards, or in a separate CSV. If multiple Projects belong to one Company, we create a Trello Workspace per Company and nest Boards under it.

Function Point Contacts are linked to Companies and contain name, email, phone, and role information. Trello Members are workspace-level users with display name and avatar. We extract Contacts and provision them as Trello Members in the workspace, mapping email to Trello's invite system and role to the Member's bio or a Label on Cards where they are assigned. Contact notes are migrated as Card comments on relevant Cards.

Function Point Briefs hold project briefs and creative direction as unstructured text. Trello Cards support rich-text descriptions. We extract Brief content per Project/Job and populate the Board description or the first List's first Card description with the Brief text, chunked as needed. Large Brief documents that exceed Trello's description field length are documented in the manual-recovery workbook with a link to the source system.

Function Point Notes attach to Companies, Contacts, Projects, and Jobs as free-text entries. Trello Card Comments hold threaded discussion. We extract Notes and append them as Card Comments on the corresponding Trello Card, with a header indicating the original Note's author and creation date. Long notes are chunked to fit Trello's comment length limit. Notes on Companies and Contacts with no direct Card association are linked via description entries on the relevant Board.

Function Point maintains a service catalog (Service Groups and individual Services with rates) used in Estimates. Trello Labels serve as a categorical tag. We extract the full service catalog and map Service Groups to Label colors and Service names to Label text. The rate per service is preserved in the manual-recovery rate spreadsheet. Customers who need service catalog precision post-migration should use a Trello Power-Up for product or service lookup.

Function Point's REST API explicitly excludes custom fields on Companies and Contacts; this is a documented design exclusion, not a temporary limitation. We cannot read these values via API. We flag all instances during scoping, export the data via CSV from the module Find page, and provide a manual-entry plan for the customer's admin to apply custom field values in Trello as Labels, Custom Fields (on Standard and above), or Card descriptions. This step adds one to two business days to the migration timeline.