Migrate from PROAD to monday Work Management

PROAD Projects map 1:1 to monday.com Boards. The project name becomes the board title, description migrates as the board description, status maps to a Status column, and start/end dates map to a Timeline column if the customer uses the Timeline view. We create the board structure (Groups, columns) during the sandbox pass so that nested Subprojects and Tasks can be imported in dependency order.

PROAD Subprojects nest within Projects and carry their own task hierarchies. We map each Subproject to a monday.com Group within the parent Board. Milestone dates within the Subproject migrate as date columns or Timeline column entries on the Group header. If the Subproject has more than 200 Items, we may split it across multiple Groups to stay within monday.com's recommended item density per Group for performance.

PROAD Client records bundle company information and primary contact details. We split these into monday.com Company records (for the organization) and Contact records (for the individual). The primary contact within the PROAD Client record becomes the primary Contact linked to the Company. If the customer uses monday CRM alongside Work Management, we configure separate Contact boards; if they use Work Management only, we create a linked Contacts column on the project Board.

PROAD Tasks migrate as monday.com Items within the appropriate Group. Assignee assignments map from PROAD's task assignee list to monday.com's People column. Due dates map to the Date column, priority levels map to a Priority column or Status label, and subtasks within a PROAD Task nest as Subitems in monday.com. Task comments migrate as Item updates.

PROAD Milestones are date-based markers within a project timeline. We map them to either Group-level date headers (for milestone groupings that separate phases) or to dedicated Items with a Timeline column that marks the phase boundary. Milestone completion status migrates as a checkbox column or Status label on the milestone Item. The customer chooses the preferred display pattern during scoping.

PROAD time entries carry hours logged, the linked task or project, and user attribution. monday.com's Time Tracking column captures hours per Item but does not natively support per-project or per-user billing rates. We map time entry hours to the Time Tracking column and carry original billing rate data in custom number fields (rate_per_hour__c or project_rate__c) that the customer's admin configures based on their billing model. Billable flag from PROAD migrates as a Checkbox column.

PROAD Tickets linked to Projects or Clients migrate as Items in monday.com with the original ticket-project linkage preserved in a custom Link or Text column. Ticket status and priority map to Status and Priority columns. Conversation history migrates as Item updates with a [Ticket Note] prefix so that support teams can reconstruct the thread. If the customer licenses monday service, we map Tickets to Cases instead.

PROAD custom fields on Projects, Tasks, and Contacts require type mapping to monday.com column types. Text fields map to Text columns, numeric fields to Numbers columns, date fields to Date columns, dropdown values to Dropdown or Status columns, and checkbox fields to Checkbox columns. We inventory all custom fields during discovery, map them to equivalent monday.com column types, and flag any that have no direct equivalent for manual configuration post-migration.

PROAD user accounts map to monday.com Users matched by email address. We extract every distinct user referenced on Tasks, Subprojects, and Tickets and resolve them against the monday.com destination workspace. Inactive or suspended PROAD accounts are flagged and optionally excluded from migration based on the customer's preference. Role and permission data does not migrate because monday.com's permission model is workspace-based rather than per-project role-based.

File attachments on PROAD Tasks, Projects, and Tickets migrate as Files linked to the corresponding monday.com Item. We flag attachments exceeding monday.com's typical file size limits during the audit phase and handle them as a separate file migration pass with download links documented in a supplemental sheet. Image attachments embed directly in Item updates.

PROAD's accounting and KPI dashboards contain financial summary records that do not have a native monday.com equivalent. We migrate financial summary records as custom Items in a dedicated finance board with number columns for key metrics, and we configure monday.com Dashboards to recreate the KPI widgets from the source data. Detailed ledger entries require a separate accounting-focused migration pass if the customer moves to a dedicated accounting tool.

Tags applied to PROAD Projects, Tasks, and Contacts migrate as monday.com Labels. We normalize tag names during the transform phase to remove inconsistencies from casing or spacing that would otherwise create duplicate Labels in monday.com. The customer chooses whether Labels are applied at the Board or Item level during scoping.