Migrate from Productive to monday Work Management

Productive Projects map directly to monday.com Boards. We preserve project name, status (active/on hold/archived mapped to Board state), start and end dates, description, and the list of assigned members. Custom field values migrate to monday.com columns using the equivalent column type (text, date, number, dropdown). If the Productive project uses a specific client or client-facing naming convention, we map that to a Board Label or a dedicated Client column in monday.com.

Productive Lists within a Project map to Groups within the corresponding monday.com Board. We preserve List ordering and List-level custom fields as Group-level information (where monday.com supports it) or as a dedicated information Item at the top of each Group. Lists without a direct Group equivalent (e.g., Lists used for client invoicing grouping rather than task grouping) are flagged for the customer's admin to reorganize post-migration.

Productive Tasks map to monday.com Items. We transfer task name, status (Productive status values mapped to monday.com Status column options), assignee, due date, time estimate, and custom field values. Subtasks map as nested Items using monday.com's Subitem feature (available on Pro and above) or as Items in a separate Subtasks board linked via Connect Boards column. Parent-child task relationships are preserved as monday.com Item connections or subitems depending on the destination plan tier.

Productive Milestone dates and names migrate to monday.com as Date column values on the milestone Item, with a dedicated Status column set to a Milestone label. We use a consistent naming convention (prefixed with [M] or a milestone icon) so the customer's team can visually identify milestone Items in the Board view. If the destination uses monday.com's native Timeline or Calendar view, milestone Items appear as date markers without requiring a separate object.

Productive time entries (user, date, duration, billable flag, task association, notes) map to monday.com's Time Tracking column on Items (Pro plan and above) or to a separate Time Entries board for Standard plan destinations. We preserve the billable/non-billable flag explicitly, noting that monday.com's Time Tracking column does not have a recognized-time concept; all billable entries log directly without a separate approval or recognition step. Time entries without a task association migrate to a catch-all Time Entries board and are linked to the parent Project board.

Productive budgets (recurring and one-time, tied to Projects or Clients) have no monday.com native object. We extract budget amounts, types, and periods as a structured CSV export and deliver it alongside the migration. For teams that need budget data visible in monday.com, we map budgets to Number columns or Formula columns on the Project Board and document the calculation logic. Budget vs. actual reporting requires reconstruction using monday.com's Chart View or a third-party BI tool integration.

Productive Invoices generated from recognized time entries cannot migrate to monday.com because monday.com Work Management does not have an Invoice object. We extract invoice headers, line items, totals, payment status, and the associated time entry references as a structured export. Open invoices (with unrecognized time entries) are flagged during pre-migration audit so the customer can finalize or document them before cutover. We do not generate new invoice records in monday.com; the customer's admin sets up a separate invoicing tool post-migration if needed.

Productive Expense records (amount, date, description, category, billable flag, project and task association) map to a dedicated Expenses board in monday.com or to Item fields on the relevant Project Board using text, number, and dropdown columns. The billable flag migrates as a Status or Label column so the team can identify reimbursable vs. non-billable expenses. Expense categories map to monday.com Dropdown or Label columns with equivalent values.

Productive Rate Cards (per-role or per-person billing rates tied to tracked time) have no direct monday.com object. We extract rate card entries as a structured export (role, person, rate, currency) and deliver it alongside migration. Where the destination team wants visibility, we map rates to a Rate Card board using monday.com Items as rate entries, with Columns for role, person, rate, and currency. This is documented as a reference table, not a live billing integration.

Productive Teams (Professional+ feature) group members for resource planning. monday.com's Team feature (separate workspace or Team View) serves a similar grouping function. We preserve team memberships and map them to monday.com Teams where the destination plan supports it, or to Tags on member Items in a People Board. Team-level capacity views require reconstruction in monday.com using Workload View (Pro and above) or a third-party resource management integration.

Productive Members (name, email, role, active/inactive status) map to monday.com's People column type on Items or to a separate People Board. We preserve active/inactive status as a Status column and role as a Text or Dropdown column. Avatar and profile image are not migrated. Seat counts and permission levels are reported from Productive and handed off as documentation for the customer's admin to configure monday.com permissions accordingly.

Productive Skills (Ultimate-tier feature tagging members with competencies) map to monday.com Tags on People Board Items or to a Text column listing competencies. We preserve skill names and the member-to-skill association. Where the destination does not use Skills for resource matching, the skill list is delivered as a tag reference table. Skills do not drive any automation or assignment logic in monday.com without custom configuration.

Productive account-level custom fields (5 on Essential, 15 on Professional, more on Ultimate) map to monday.com Columns with equivalent types: text fields to Text columns, numeric fields to Number columns, date fields to Date columns, and picklist fields to Dropdown or Label columns. We pre-create the column schema in monday.com before data migration so that custom field values transfer directly into correctly typed columns. Fields that exceed monday.com's column type limits (e.g., very long text stored as a Productive custom field) are mapped to Long Text columns.