Migrate from Paymo to monday Work Management

Paymo Projects map directly to monday.com Boards. Project name, status (Active / Archived), client association, budget, and hourly rate migrate as board metadata or custom columns. We create the board in the appropriate Workspace and preserve the project start/due date as a Timeline column if the destination plan supports it. Archived Paymo projects map to archived monday.com boards.

Paymo Task Lists map to monday.com Groups within the board. The group name and ordering within the board are preserved. If a Paymo project contains multiple Task Lists with shared milestone references, we ensure the Group sequence matches the source ordering so milestone display positions remain consistent with the original project structure.

Paymo Tasks map to monday.com Items. Standard fields including name, description, start/due dates, estimated hours, assignee (User Assignment), priority, and status migrate to equivalent monday.com columns (Text, Date, Numbers, Person, Status). Custom task fields migrate as monday.com custom columns of the matching type. The task's status value maps against the destination board's Status column, which is configured to match the source project's workflow.

Paymo Time Entries are Many-to-One against Tasks. We map time entries to monday.com Subitems when the destination plan supports Subitems, preserving date, duration (in hours), billable flag, hourly rate, and description. If Subitems are unavailable on the target plan, we use an Item-level Time Tracking column and append a note with the original duration and billable status. The task-to-item linkage is preserved so time-entry context is attached to the correct work item.

Paymo Clients are separate records linked to Projects and Invoices. We map Clients to monday.com Contacts (on plans with Contacts enabled) or to a Location column on the board. Client name, email, phone, address, and billing information migrate to matching fields. If the destination uses Contacts, we resolve the Project-to-Client linkage by adding the Contact as a Person column or as an integration-linked Contact record on the board.

Paymo's Custom Workflows (introduced March 2026) define per-project Kanban status columns. Each project may have a different set of statuses. We create a monday.com Status column per board and populate it with the exact status labels from the source project's workflow. Any statuses that have no direct equivalent in monday.com's default status set are added as custom labels and flagged in the migration report for the customer's review.

Paymo Milestones are tied to Task Lists and display after the Task List in Gantt view. We map milestones to the monday.com Milestone app or to a Timeline column with a single-date marker. Milestone names and their Task List parent association are preserved. Because Paymo anchors milestones to Task Lists rather than individual tasks, milestone display in the destination may appear shifted relative to individual task dates; we flag this for manual post-migration review.

Paymo Project Templates bundle a project structure including Task Lists, Tasks, and workflows for reuse. We migrate the template structure as a monday.com Board Template, preserving the Task List hierarchy, default Task fields, and workflow status configuration. The customer recreates the template in monday.com's Template Center using the migrated structure as a reference.

Paymo Discussions are project-level comment threads attached to Projects. We migrate discussion content as comments on the corresponding monday.com board or on individual Items within the board, preserving chronological order and author attribution. Discussion threads with multiple replies are collapsed into sequential comments. Attachments referenced in discussions migrate as file links if the file URLs are accessible.

Paymo User Assignments on Tasks and Projects map to monday.com Person columns. We resolve assignees by email match against the monday.com workspace members. Users without a matching monday.com account go to a reconciliation queue for the customer's admin to provision before item import resumes.

Paymo Invoices are generated from Time Entries and carry client, line items, totals, tax, and payment status. monday.com has no native Invoice object. We export Paymo Invoices as a structured CSV and JSON supplementary package, including invoice number, client name, line item descriptions, amounts, tax, and status. The customer recreates invoices in monday.com manually or uses the export with a connected accounting integration (QuickBooks, Xero, FreshBooks). We flag any invoices with disconnected client records that require manual client matching.

Paymo Estimates are project-level financial approximations available on Small Office and Business tiers. We map estimates to monday.com Items with a structured numeric or currency column capturing the estimate amount, and a status column for the estimate state (Draft / Sent / Accepted / Rejected). The link between an Estimate and the source Project migrates as a reference column on the board.

Paymo Leave Planner manages employee time off and feeds the scheduling workload view on Business plan. monday.com has no native leave management module. We export Leave Planner records as a supplementary CSV including employee name, leave type, start date, end date, and hours. The customer uses this export to configure leave data in an HR system or to recreate leave-based blocks manually in monday.com's Calendar view.

Paymo Expenses are project-level cost records separate from time entries, with amount, date, description, and billable status. We map expenses to monday.com Items with a Number or Currency column for the amount, a Date column for the expense date, and a Status or Labels column for the billable flag. Expenses are placed in a dedicated Group or a separate board depending on the customer's preference during scoping.