Migrate from CRM Runner to monday CRM

CRM Runner Contact records (name, email, phone, address, custom fields) map directly to Monday.com CRM Contacts. We extract via UI-based data pull during scoping and import via Monday.com Contacts API. Any CRM Runner custom fields on contacts become Monday.com Contact column fields. The CRM Runner contact-to-company relationship is preserved by linking the Monday CRM Contact to a Company record created from the CRM Runner Company object.

CRM Runner Company records map to Monday.com CRM Companies. Company name becomes the Company name field; domain or website maps to a URL column. We import Companies first so that the contact-to-company linkage is established before Contact import begins. CRM Runner contacts without a company assignment link to a Default Company or remain unlinked per the customer's scoping decision.

CRM Runner Job records are the most structurally complex object to map. Jobs contain embedded fields (job status, location, assigned team members, time entries, customer, description) that CRM Runner stores as sub-records. We flatten these into Monday.com Board Items using a custom column structure: status column for job stage, location text columns, a people column for assigned Team Members, date columns for scheduling, and long-text columns for job notes. Job status values from CRM Runner map to Monday.com status column values that we configure during board setup.

CRM Runner Team Member records (name, email, role, department, permission level) map to Monday.com Users for board and item assignment purposes. We extract all Team Members during discovery and provision them as Monday.com workspace members before job and task import. Permission levels from CRM Runner do not map directly to Monday.com's permission model; we document the original permission structure as a written artifact for the customer's admin to reconfigure in Monday.com Workspace Settings.

CRM Runner embeds call logs, SMS threads, and in-app chat history within contact or job records. We extract these as discrete activity records, classify by type (call, SMS, chat), and import them into a dedicated Monday.com Activities Board as Items with columns for type, timestamp, contact reference, related job, and content. Alternatively, for smaller volumes, activity summaries append as updates to the Contact or Job Item in Monday.com using the Update column. The customer chooses the approach during scoping based on activity volume.

CRM Runner Task records (due date, assignee, status, description) map to Monday.com Items in a Tasks board or as Subitems attached to the related Contact or Job Item. We preserve the assignee mapping by resolving CRM Runner Team Member email to Monday.com User. Due dates migrate as Date column values. Task status from CRM Runner maps to a Status column that we configure to match the customer's original task workflow.

CRM Runner supports custom fields on contacts, companies, and jobs. We extract all custom field definitions during scoping, classify each by data type (text, number, date, checkbox, dropdown), and recreate them as Monday.com column types (Text, Numbers, Date, Checkbox, Dropdown/Label) on the relevant boards. CRM Runner multi-select or tag-style custom fields map to Monday.com Tag column. Any custom field that has no Monday.com equivalent (e.g., complex conditional logic fields) is documented as a custom-column workaround or flagged for rebuild as an Automation.

CRM Runner pipeline stages (configurable per pipeline) map to Monday.com Board Status column values. We extract the full stage name list and order during scoping, configure the Status column with matching values during board setup, and preserve any stage-specific probability or completion flag as additional Status column groups. CRM Runner's multi-pipeline support maps to separate Monday.com Boards, each with its own Status column.

CRM Runner time-clock records (clock-in, clock-out, duration, tied to Team Member and Job) do not map cleanly to Monday.com CRM objects. We export time entries as a separate CSV package with columns for employee name, job reference, date, clock-in time, clock-out time, and total duration. The customer can import this CSV into a Monday.com Time Tracking board if they have the Time Tracking add-on, or use the data in a dedicated payroll or time-tracking tool. This export is not part of the standard CRM migration scope and is delivered as a companion artifact.

CRM Runner automations (trigger-action logic) are not migratable to Monday.com Automations or any other platform because they are not exposed via a documented API or export endpoint. We document every automation identified during discovery as a written specification: trigger type, conditions, and actions. The customer's admin uses this document to rebuild automations in Monday.com Automations, which uses a visual recipe builder with conditional triggers and actions per board. Automation quotas by plan tier should be verified against the count of existing CRM Runner automations.