Migrate from CRM Runner to Freshsales

CRM Runner Contacts map to Freshsales Leads or Contacts based on business context. We recommend that unqualified prospects (new leads, referrals without a deal) land as Freshsales Leads while existing customers and anyone with a history of booked Jobs land as Contacts attached to an Account. We preserve CRM Runner contact fields (name, email, phone, address, custom fields) on the target record and flag any contacts without a matching Freshsales Account for manual linking post-migration.

CRM Runner Company records map directly to Freshsales Accounts. The Account Name, Website, Industry, Phone, and Address fields transfer 1:1. Custom fields on CRM Runner Company map to Freshsales custom fields on Account. We use company name as the dedupe key during import to prevent duplicate Account creation when multiple CRM Runner contacts reference the same company.

CRM Runner Jobs are the primary field-service object, carrying work order status, assigned Team Members, location, time entries, and payment records. Freshsales does not have a native work orders object. We map Jobs to Freshsales Deals with a custom field job_status__c carrying the original job lifecycle stage (Scheduled, In Progress, Completed, Cancelled). If the customer requires full field-service tracking, we pre-create a Freshsales custom object called Work_Orders__c with fields for job number, status, assigned technician, location, and time entries. The mapping decision is made during discovery based on how the customer uses Jobs in CRM Runner.

CRM Runner Team Members map to Freshsales User records. We resolve by matching email address. CRM Runner roles (Admin, Technician, Manager) map to Freshsales role assignments and profile permissions. Any CRM Runner Team Member without an email match in Freshsales is held in a reconciliation queue for the customer's admin to provision before record import resumes. Team Members who do not need CRM access (payroll-only records) are exported as a separate artifact for payroll or HR system processing.

CRM Runner Tasks migrate to Freshsales Tasks with Subject, Due Date, Assignee (resolved via Team Member-to-User mapping), Status, and Priority preserved. Tasks associated with a Job carry the parent Job/Deal reference in the Freshsales WhatId field.

CRM Runner stores call logs, SMS threads, and in-app chat as discrete Communication records attached to Contact or Job. We flatten these into Freshsales Task records with TaskSubtype set to Call for phone logs, and the message content stored in the Task description or a custom field. Call duration and disposition migrate to custom task fields. SMS thread content migrates as separate Task records ordered by timestamp to preserve conversation chronology.

CRM Runner custom fields on Contacts, Companies, and Jobs are extracted during scoping and mapped to Freshsales custom fields of equivalent type. Text fields map to Freshsales text fields, number fields to number fields, date fields to date fields, and multi-select or checkbox fields to Freshsales multi-select picklist or checkbox fields. We create the destination custom fields in Freshsales before migration begins. Any CRM Runner custom field without a clear Freshsales equivalent is flagged as a gap item with a recommended fallback (custom field, description field concatenation, or notes field).

CRM Runner embeds time-clock records (clock-in, clock-out, duration) within Jobs and Team Members rather than as standalone objects. These are payroll-adjacent and do not map to standard CRM activity objects in Freshsales. We extract time entries as a separate CSV package with Team Member reference, Job reference, date, and duration. The customer processes this through a payroll or accounting tool. If the customer requests it, we can attach the time CSV as a related record to the corresponding Work_Orders__c custom object in Freshsales.

CRM Runner pipeline stages map to Freshsales Deal stages. We configure Freshsales Deal stages to match the CRM Runner stage names and order during migration. Any custom stage logic (auto-assignment, stage-specific notifications) is documented as a workflow specification for Freshsales workflow rebuild.