Migrate from CRM Runner to Zoho CRM

CRM Runner Contact records (name, email, phone, address, custom fields) map directly to Zoho CRM Contacts module. The primary email address becomes the dedupe key. Custom fields on CRM Runner contacts migrate as Zoho CRM custom fields on the Contacts layout, with field type mapped (text to single-line, multi-select to picklist, date to date field). CRM Runner contact-to-company relationships preserve by matching on company name or external ID during the Companies phase.

CRM Runner Company records map to Zoho CRM Accounts. We extract the company name, domain, address, and any associated custom fields. Account is created before Contact import so the Account-Contact lookup relationship is satisfied at the moment of Contact insert. The CRM Runner contact-company linkage migrates as a Zoho lookup field on the Contact record.

CRM Runner Jobs are the primary field-service object, carrying work order data, job status, assigned team members, location, and embedded time entries. Jobs with a status indicating an open service request map to Zoho CRM Deals with a custom Job Status field preserved, and the job description becomes the Deal name. Jobs that represent discrete one-off tasks map to Zoho Tasks with the Team Member assignment carried as Owner. The split rule is defined during scoping based on the customer's job type taxonomy. Location data migrates to the Deal's address fields or a custom multi-line address field.

CRM Runner Team Member records (employee name, role, department, permission level) map to Zoho CRM User accounts. We match Team Members by email address against Zoho Users. Role and department from CRM Runner migrate as custom fields on the Zoho User record. Permission profiles require manual reconfiguration in Zoho because CRM Runner's permission model and Zoho's role-based access control (data sharing rules, field-level security, and profile assignments) are structurally different. We flag every permission gap as a reconciliation item for the customer's admin.

CRM Runner time-clock records are embedded within Jobs and tied to Team Members. They do not map to any standard Zoho CRM object without significant custom field overhead. We extract time entries as a separate CSV package (Employee, Job Reference, Clock In, Clock Out, Duration, Notes) and recommend migrating this data to Zoho Payroll or a dedicated time-tracking tool. The CSV package is included in the migration artifact delivery and the customer decides whether to load it into Zoho or a separate system.

CRM Runner embeds call logs, SMS threads, and in-app chat as discrete records attached to contacts or jobs. We extract these as structured activity records and flatten them into Zoho CRM Activities: calls become Task records with Task Subtype set to Call, with disposition, duration, and recording URL stored in custom fields; SMS threads become Task records with the full message thread stored in the description field; in-app chat becomes Note records linked via multi-select lookup to the relevant Contact or Deal. The original timestamp preserves as Activity Date for timeline ordering.

CRM Runner Task records (due date, assignee, status, description) map directly to Zoho CRM Tasks. Assignee mapping resolves CRM Runner Team Member to Zoho User by email. Status values map from CRM Runner's task states to Zoho's Open, Overdue, and Completed status taxonomy. The original CRM Runner task ID preserves as a custom field for reconciliation during parallel-run.

CRM Runner pipeline stages migrate as Zoho CRM Pipeline stages under the Deals module. Stage names and order map from CRM Runner to Zoho Pipeline Configuration. Any custom stage logic in CRM Runner (such as automated status transitions) is documented as a written specification for rebuilding in Zoho's Blueprint visual process builder, which operates on the same stage-transition model.

CRM Runner custom fields on contacts, companies, and jobs migrate as Zoho CRM custom fields on the equivalent modules. We extract all custom field definitions during scoping and map field types to Zoho's field type taxonomy. Custom fields with no direct Zoho equivalent (such as CRM Runner-specific dropdown values) map to a custom picklist or multi-select field and we flag any orphaned picklist values for the customer's admin to resolve in Zoho's field settings.

CRM Runner automations are configured through a trigger-action interface with no documented export endpoint. We do not migrate automations as code. We document every identified automation as a written specification: trigger type, conditions, actions, and affected records. This inventory is delivered alongside the migration and the customer's admin rebuilds the automations in Zoho Workflow Rules or Blueprint. Standard migration timeline does not include automation rebuild; this is a post-migration implementation step.

CRM Runner embeds payment records within Jobs or Contacts. These are accounting-adjacent and do not map to standard Zoho CRM objects. We export payment data as a separate financial CSV package (Transaction ID, Contact Reference, Job Reference, Amount, Payment Method, Date, Status) and recommend migrating this data to Zoho Books or a dedicated accounting platform. This export is delivered as a migration artifact but is outside the CRM migration scope.