Migrate from CRM Runner to Pipedrive

CRM Runner Contacts map directly to Pipedrive People. We extract name, email, phone, address, and all custom field values during UI-based scoping and map them to Pipedrive Person fields using exact field-name matching where available and custom field mapping where CRM Runner uses non-standard field names. The Person's organization_id is resolved post-import by matching the CRM Runner contact's linked Company name to the Pipedrive Organization name.

CRM Runner Company records map to Pipedrive Organizations. The company name becomes the Organization name field and serves as the dedupe key during import. We preserve any CRM Runner custom fields on the company record as Pipedrive custom fields on Organization, using the CRM Runner field label as the Pipedrive field name for consistency.

CRM Runner Jobs (work orders with status, assigned team members, location, and embedded time entries) map to Pipedrive Deals as the primary pipeline object. The job title becomes the Deal title, job status maps to a Pipedrive pipeline stage, and the assigned team member becomes the Deal owner resolved via email match to Pipedrive User. Job-specific data — service type, location address, and job notes — migrate as Deal notes and custom fields. Because a single CRM Runner Job may represent work spanning multiple Pipedrive Deals (for multi-phase service agreements), we flag any such Jobs during scoping for the customer to confirm split strategy before import.

CRM Runner Team Members map to Pipedrive Users by email match. Role and department from CRM Runner become a custom field on the Pipedrive User record. Permission levels do not map automatically — we flag the CRM Runner admin and standard-user permission distinctions and deliver a written mapping table for the customer's Pipedrive admin to configure role-based access control manually post-migration.

CRM Runner Tasks map directly to Pipedrive Tasks with due date, assignee (resolved via email match to Pipedrive User), status, and priority preserved. CRM Runner task content migrates as the Pipedrive Task subject and notes field. Completed and open task counts are reconciled against the source before production migration.

CRM Runner call records (duration, disposition, recording URL if stored) map to Pipedrive Activity records of type call, linked to the associated Person (contact) and Organization. Call logs that reference a specific Job inherit the Deal created from that Job. We preserve the call timestamp as the Activity date for timeline ordering.

CRM Runner SMS threads are extracted as Activity records with type note or a custom activity type depending on the customer's Pipedrive plan. The SMS body becomes the activity content, linked to the associated Person and Organization. We flag any SMS threads that reference a Job and document the association for manual linking to the migrated Deal during post-migration review.

CRM Runner time-clock records (clock-in, clock-out, hours worked, tied to Team Members and Jobs) have no standard Pipedrive CRM equivalent. We export these as a separate CSV package with Team Member name, Job title, date, clock-in, clock-out, and hours worked columns. The customer should route this data to a payroll or accounting tool rather than the CRM. We flag this clearly in the migration scope and recommend a paired payroll migration if the time data is business-critical.

CRM Runner payment records embedded within Jobs (transaction amount, status, payment method) do not map cleanly to any Pipedrive standard object. We export payment data as a separate financial CSV package linked to the corresponding Job ID so it can be reconciled against the migrated Deal record. The customer should migrate this data to an accounting tool (QuickBooks, Xero, or similar) rather than the CRM.

CRM Runner custom field definitions on Contacts, Companies, and Jobs are extracted during scoping as a named field list with type and options. We create matching Pipedrive custom fields on the corresponding objects (Person, Organization, Deal) before migration, preserving field type where possible (text, number, date, dropdown). Any CRM Runner dropdown fields with options become Pipedrive drop-down custom fields with the same options list.

CRM Runner pipeline stage names and order map to Pipedrive Pipeline stages. Stage probability percentages from CRM Runner migrate to Pipedrive stage probability values. If CRM Runner has multiple pipelines (multiple sales or service lines), we create corresponding Pipedrive Pipelines and map each CRM Runner pipeline to its Pipedrive equivalent during scoping.