Migrate from Function Point to monday Work Management

Function Point Companies map to Items in a monday.com Clients board. We preserve company name, address fields (street, city, state, postal code, country), primary contact email, phone, and the assigned account-rep owner. monday.com has no native Company or Account object in Work Management, so we configure a custom board with columns matching the source schema. The client's domain or website URL is stored in a text column as a dedupe reference. This board serves as the parent for all related Project boards via monday.com's Connect Boards or Link to Item column.

Function Point Contacts map to the monday.com Person column type within the Client board (one Person per Item), or to Items in a separate Contacts board linked to the Client board via Link to Item. We preserve first name, last name, email, phone, role/title, and the relationship to the parent Company via the link. Notes attached to Contacts migrate as long-text Update notes on the Item. If Function Point uses custom fields on Contacts, these require CSV extraction and manual entry because the Function Point API cannot read them.

Each Function Point Project becomes a monday.com Board. We preserve project name, start and end dates (mapped to Board date range or to Date columns on the board header group), project status, and budget fields. The board is linked to its parent Client Item via Connect Boards so that client-level reporting can aggregate across all project boards. Project-level budget tracking requires a custom numeric column with a formula or a manual dashboard aggregation because monday.com does not have a native budget field.

Function Point Jobs are the primary work-order unit inside a Project and are best modeled as Groups inside the Project board in monday.com. Each Job becomes a Group, and the Tasks belonging to that Job become Items within the Group. We preserve Job name, assigned owner, cost codes, status, and the link to the parent Estimate. If the agency has multiple simultaneous Jobs per Project and wants Job-level financials visible, we create a separate Job-level board linked back to the Project board rather than using Groups, but this adds configuration complexity and is decided during scoping.

Function Point Tasks migrate as Items inside the appropriate Job Group. We preserve task name, description (as Item Updates or rich-text column), due date, assigned user, status, and priority. Custom task-status labels in Function Point are value-mapped to monday.com Status column values. Dependencies between Tasks are preserved via monday.com's Dependency column type. Tags on Tasks migrate to a Labels column.

Function Point Estimates contain line items with service names, quantities, rates, and markup percentages, linked to the parent Job. monday.com Work Management has no native Estimate object. We create a separate Estimates board with Items representing each Estimate, linked to the parent Project board via Connect Boards. Each line item becomes a sub-item or row with Service, Quantity, Rate, Markup %, and Total columns. We extract the full rate table and markup schedule from Function Point during scoping and create a custom mapping that your team reviews before applying rates to imported Estimates. This adds one to two business days to the migration timeline.

Function Point Expenses (vendor, amount, date, description, attached receipt reference) migrate as Items in a separate Expenses board linked to the Project or Job board. We separate posted and unposted Expenses by adding a Status column (Posted/Unposted) matching Function Point's status distinction. Expenses linked to a specific Job carry a Link to Item reference to that Job Group so the financial relationship is preserved. The customer should verify that any receipt attachments are accessible for re-upload or manual re-attachment in monday.com.

Function Point Timesheet entries (user, date, hours, Job/Task association, billable/non-billable flag) migrate via monday.com's native Time Tracking column on each Item. If the agency requires timesheet reporting across multiple Jobs, we also create a Timesheet board with Items representing each timesheet entry, using the Person column for the user, Date column for the date, and a numeric column for hours, linked to the Job Item. We preserve the billable/non-billable flag as a Labels column (Billable/Unbillable) or as a separate toggle column type.

Function Point 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 confirmed billing records in an Invoice board with status set to Paid or Partial; Draft invoices map to status Unpaid or Pending Review. monday.com Work Management does not have native invoice generation, so the Invoice board stores historical billing records for reference rather than acting as a billing system. Any invoice PDFs stored in Function Point are flagged for manual re-upload.

Function Point Briefs hold project briefs and creative direction as unstructured content. We export Briefs as text content and map them to monday.com's Document integration (monday docs) or as a long-text column on the Project board's header Item. Large Brief documents may require chunking if they exceed monday.com's text field limits. We flag any Brief that exceeds 5,000 characters for manual review during scoping.

Function Point maintains a service catalog used in Estimates. We export Services and their associated Rates and create a Services board in monday.com with Items representing each service, including Rate and Unit columns. This board acts as a reference catalog for creating Estimates rather than a native integration, since monday.com does not have a product or service price list feature. Rate markup percentages from Function Point are stored in a Markup % column on the Services board.

Function Point's REST API explicitly excludes custom fields on Companies and Contacts. We flag all such instances during scoping, export the data via CSV from the module Find page, and provide a manual-entry plan: we document the exact field names, data types, and values so your team can create matching custom columns in monday.com and populate them manually. This is not an automated step. We deliver the CSV and a field-by-field mapping guide as part of the migration handoff package.