Migrate from CRM Runner to HighLevel

CRM Runner Contact records (name, email, phone, address, and custom fields) map directly to GoHighLevel Contact. The CRM Runner contact-to-company linkage is preserved via the Company Name field in GoHighLevel Contact. Custom fields on CRM Runner contacts migrate to GoHighLevel Contact custom fields, which must be created before import. Contact custom fields and Opportunity custom fields in GoHighLevel are distinct and once created cannot be switched — we create Contact custom fields during schema setup for CRM Runner contact-level data.

CRM Runner Company records map to GoHighLevel Contacts with the Contact Type set to Company, preserving the CRM Runner company name and any company-level address or custom fields. We use company name as the dedupe key during import. The CRM Runner contact-to-company relationship is maintained by matching Contact records against the migrated Company name in GoHighLevel.

CRM Runner Jobs is the primary field-service object tracking work orders, job status, assigned team members, location, and embedded time entries. GoHighLevel has no native Jobs object — the mapping requires a design decision during scoping. We offer two paths: map Jobs to GoHighLevel Opportunities with custom fields (job_status, assigned_technician, location, job_date) added to the Opportunity, or create a custom object (Work Order or Job) in GoHighLevel. The choice depends on whether the team wants job data visible in the pipeline view or as a separate object. Custom objects in GoHighLevel are available at all paid tiers.

CRM Runner Team Member records (employee name, role, department, permission level) map to GoHighLevel Users. We resolve by email match. Permission profiles and role assignments from CRM Runner are documented as a written specification for manual reconfiguration in GoHighLevel because the permission models differ structurally. Team Members with GPS tracking and time-clock data export separately.

CRM Runner Task records (due date, assignee, status, description) migrate to GoHighLevel Tasks 1:1. Assignee mapping resolves by matching CRM Runner Team Member email to GoHighLevel User email. Tasks linked to specific Jobs carry the Job reference as an Opportunity lookup or custom object lookup depending on the Jobs mapping path chosen during scoping.

CRM Runner call logs, SMS threads, and in-app chat attached to Contacts or Jobs flatten into GoHighLevel Activity records. Call recordings are documented as file paths for manual re-attachment since the recording storage mechanism differs between platforms. SMS threads migrate as text activity entries with direction (inbound/outbound) preserved. The CRM Runner contact or job reference maps to the GoHighLevel Contact or Opportunity lookup.

CRM Runner time-clock records (clock-in, clock-out, hours worked) are embedded within Jobs and Team Members rather than exposed as standalone objects. We extract them as a separate CSV package during migration scoping. Time entries do not map to a standard GoHighLevel CRM object — they are exported as a payroll-adjacent dataset for import into a dedicated time-tracking or accounting tool. We recommend pairing the CRM migration with a separate payroll tool migration for these records.

CRM Runner custom fields on contacts, companies, and jobs are extracted as field definitions during scoping and created as equivalent GoHighLevel custom fields. CRM Runner supports text, date, checkbox, and dropdown field types — all map to GoHighLevel custom field equivalents. Custom fields must be created before data import begins. CRM Runner custom field labels are preserved in GoHighLevel for recognition, and any CRM Runner field with no GoHighLevel equivalent is flagged in the mapping artifact for customer decision.

CRM Runner pipeline stages (configurable per object) map to GoHighLevel Pipelines and Stages. Stage names and ordering migrate from CRM Runner to GoHighLevel. Custom stage logic (conditional visibility, stage-specific fields) is documented as a workflow rule specification for manual rebuild in GoHighLevel's automation builder.

CRM Runner automation rules (trigger-action logic configured in the platform) are documented as a written specification with trigger type, conditions, and actions for manual rebuild in GoHighLevel Workflows. Automations do not migrate as code because the automation models are structurally different. We deliver the full automation inventory at migration close.