Migrate from Road Runner to Pipedrive

Road Runner's person object maps directly to Pipedrive's Person object. All standard fields — name, email, phone, address — copy over. Road Runner stores the primary organization as a nested org_id; we resolve this to Pipedrive's org_id after organizations land. Owner resolution happens by email match against Pipedrive users before records commit.

Road Runner organizations map to Pipedrive Organizations. We preserve parent-child hierarchy using Pipedrive's parent_org_id field. Road Runner contacts linked to multiple organizations in Road Runner collapse to one primary org_id link; additional org associations surface as linked Organization records in Pipedrive's contact detail view.

Each Road Runner deal migrates as a Pipedrive Deal. The deal's pipeline_id and stage_id in Road Runner map to Pipedrive's Pipeline and Stage by matching pipeline name and stage label. Deal value, expected close date, weighted value (if Road Runner stores it), and custom deal fields all carry over. Lost and won status is preserved using Pipedrive's status field.

Road Runner pipelines map 1:1 to Pipedrive Pipelines. Each pipeline's ordered stages transfer as Pipedrive Stage objects within that pipeline, preserving stage name, position order, and rotten_days threshold. Probability values per stage are optionally mapped from Road Runner stage metadata if present in the API response.

Road Runner stage names per pipeline map to Pipedrive Stage labels by pipeline pair. Probability values and forecast category assignment are configured in Pipedrive per stage and can be sourced from Road Runner's stage metadata where available. Stage-entered timestamps are preserved as custom datetime fields in Pipedrive if the source data includes them.

Road Runner logged calls migrate as Pipedrive Activities with type='call'. The original call outcome, duration, and owner are preserved. The activity links to the correct Person or Deal by matching the Road Runner record ID stored on the Pipedrive side. Scheduled calls create a future-dated task in Pipedrive's activity timeline.

Road Runner email activities migrate as Pipedrive Activities with type='email'. The original subject line, body content, sender address, and recipient list are all preserved during import. Once migration completes, Pipedrive's native email sync feature monitors the connected mailbox and attaches all subsequent incoming and outgoing replies to the matching activity thread, keeping the conversation history intact within Pipedrive's activity record for each contact.

Road Runner meeting activities and standalone notes migrate as Pipedrive Activities with type='meeting' or type='note' respectively. Original timestamps, meeting attendee lists, and note body content copy over completely. For scheduled meetings, the start datetime and end datetime from Road Runner populate Pipedrive's due_date field, ensuring the calendar view reflects the original scheduled time. Standalone notes retain their original creation timestamps in Pipedrive's create_time field.

Road Runner custom fields on the Person object — such as lead source, rating, or any industry-specific property — require pre-creation in Pipedrive as custom Person fields. Pipedrive assigns a hash-based key to each custom field; the migration plan maps each Road Runner field key to the corresponding Pipedrive hash so values land in the right fields during import.

Road Runner custom fields on deals — discount codes, competitive flags, contract type — migrate as Pipedrive Deal custom fields. Field type translation applies: Road Runner pick-list fields map to Pipedrive enum fields, numeric fields map to Pipedrive number fields, and free-text fields map to Pipedrive text fields.

Road Runner file attachments linked to people, organizations, or deals are downloaded and re-uploaded to Pipedrive's file storage linked to the corresponding record. Pipedrive's file size limit is 150 MB per file. Files are associated by parsing Road Runner's attachment metadata to identify parent object and record ID.

Road Runner owner IDs are resolved by email address against Pipedrive users. If a Road Runner owner email has no matching Pipedrive user, the record is assigned to the migration fallback owner and flagged in the pre-migration report for your team to create the Pipedrive user or reassign manually before go-live.

Road Runner's internal record IDs are stored in a Pipedrive custom field for traceability. This enables delta-run deduplication: if a record is modified in Road Runner during the delta-pickup window, FlitStack matches by source system ID and updates the Pipedrive record instead of creating a duplicate.

Road Runner workflow definitions retrieved via API do not have a direct equivalent in Pipedrive's data model. We export workflow definitions as a JSON reference document your Pipedrive admin can use to rebuild triggers and actions in Pipedrive Automations or Sequences. No automation logic executes during the migration itself.