Migrate your Paymo data

Projects are the top-level container in Paymo. They include project-level metadata such as status, budget, hourly rate, client association, and project templates. We map Projects directly to the destination project's object and preserve the client linkage. Export via CSV or API is documented in Paymo's help center.

Task Lists are groupings of Tasks within a Project. They are ordered and carry their own name. We preserve the grouping structure and ordering when migrating to a destination that supports hierarchical task organization.

Tasks carry name, description, start/due dates, estimated hours, assignees, priority, and status derived from the project Workflow. Custom task fields are available on higher tiers. We map standard fields 1:1 and flag custom fields for field-level mapping.

Time Entries are linked to Tasks (Many-to-One) and carry date, duration, billable flag, hourly rate, and description. Invoices reference Time Entries by invoice_item_id. We preserve the task linkage and billing metadata. The feamster/paymo-mcp tool documents the invoice_item_id relationship that ties entries to invoices.

Invoices are generated from Time Entries and carry client, line items, totals, tax, and status. Paymo supports exporting invoices to QuickBooks Online via direct integration. We preserve invoice numbers, line items, and payment status. The client and item names must be matched in QuickBooks on export.

Clients are separate records linked to Projects and Invoices. Paymo supports exporting the Client list as CSV from the Clients > Table view with column selection. We map Clients to the destination account/contact object and preserve the project association.

Introduced in March 2026, Custom Workflows define per-project Kanban status columns. Projects can have different workflow sets. We map each workflow's status set to destination columns, flagging statuses with no direct equivalent. Existing projects using custom columns were auto-migrated to the Workflows feature.

Milestones mark key project stages and are tied directly to Task Lists in Paymo. They display after the task list, not at individual task endpoints. We preserve milestone names and their task list association but note that destination display behavior may differ.

Project Templates bundle a project structure including task lists, tasks, and workflows for reuse. Available on Small Office and Business tiers. We migrate the template structure as a project skeleton and note that template-to-active-project conversion depends on destination template handling.

Tasks and Projects carry Assignee fields referencing Users. Paymo's User object includes name, email, and role. We map assignees to destination user records by email, flagging any unmapped users for review.

Discussions are project-level comment threads attached to Paymo Projects. We migrate discussion content as comments or activity feed entries in the destination, preserving the chronological order but noting that threaded vs. flat comment structure may differ.

The Leave Planner is available on the Business plan and manages employee time off. Available hours are used in the scheduling workload view. We map leave records to the destination absence/HR module and preserve the date ranges and leave type classification.

Estimates are project-level financial approximations that can be converted to invoices. Available on Small Office and Business tiers. We migrate estimates as draft invoices or structured line items, preserving quantities, rates, and totals.

Project expenses are logged separately from time entries and can be billed to clients. We migrate expenses as line items or cost records, preserving amount, date, description, and billable status.