Migrate from Regal.io to Pipedrive

Regal Contacts with a phone number and a qualified engagement history map to Pipedrive Person (People). Contacts without a phone number — which were non-contactable in Regal and ineligible for Journey enrollment — map to Pipedrive Lead as inactive records with a migration flag noting their original Regal status. We run this split at migration time using the phone number presence check from the source export, preserving all standard Contact fields (name, email, phone, address) and any Regal-specific identifiers as a custom field regal_contact_id__c on the destination record.

Regal's tenant-specific custom profile fields stored on Contacts map to Pipedrive custom fields on the Person object. We extract the full attribute schema from Regal's API before migration, map each attribute to an equivalent Pipedrive custom field (with appropriate type: text, number, date, picklist), and provision the destination fields before the Person import begins. Custom field naming follows Pipedrive conventions and preserves the original Regal attribute label in a field description for admin clarity.

Regal Events — call dispositions, SMS messages, email opens, Journey step completions, and custom behavioral events — map to Pipedrive Activity records with the event type preserved as an Activity subject prefix (e.g., '[Journey Step] Application Started') and the original event timestamp as the Activity date. This preserves the chronological sequence of the contact's behavioral history in the Pipedrive Activity timeline. Event properties that are not native Activity fields migrate as notes on the Activity record.

Regal Campaigns define outbound programs with list selection, cadence, and goal metrics. Campaign membership maps to Pipedrive Lead for contacts that are pre-qualified in Regal's model, and to Pipedrive Person for contacts that already have a deal association. We preserve Campaign name, goal metrics, and list membership in a custom field campaign_name__c on the destination record. Cadence and list-refresh logic is platform-specific and requires manual rebuild in Pipedrive's Workflow Automation or LeadBooster.

Regal AI Agent configurations — voice scripts, decision trees, persona settings, and handoff logic — are tied to Regal's proprietary agent runtime and cannot be downloaded via API or UI. Agent logic is explicitly excluded from migration scope. We deliver a written inventory of all AI Agent configurations including trigger conditions, script logic, and handoff rules as a reference document for manual rebuild in the destination telephony or CRM platform. Conversation outcome data and Journey trigger conditions migrate as Activity notes and custom field values so business context is preserved.

Regal call transcripts migrate as notes on Pipedrive Activity records of type 'Call'. Audio recording files migrate as attachments to the corresponding Activity where file format and size are compatible with Pipedrive's storage limits. Availability of audio files depends on Regal's retention policy and export accessibility at migration time; we confirm file availability during the pre-migration data audit. If recording files are not accessible, the transcript text is migrated as a note and the recording gap is flagged in the migration report.

Regal SMS and email conversational history associated with Contact records migrates to Pipedrive Activity records linked to the corresponding Person. SMS messages map to Activity with type 'Call' and a note prefix '[SMS]', emails map to Activity with type 'Email'. Thread continuity in Pipedrive depends on the activity being linked to the correct Person record by email address match, which we resolve at migration time using the Regal Contact's primary email address.

Regal Journeys are conditional, event-triggered sequences of voice, SMS, and email steps built in Regal's no-code Journey builder. Journeys cannot be exported as automation logic. We document Journey trigger conditions, step-by-step conditional rules, and channel sequence logic as a written step-by-step reference document for the customer's admin to reconstruct in Pipedrive's Workflow Automation or LeadBooster. Campaign membership and goal metrics migrate as custom fields on Person and Lead records.

Regal Custom Objects — defined via Settings > Data Management > Objects with custom events as the data source — map to Pipedrive custom objects of equivalent API name if the destination Pipedrive account is on Advanced tier ($29/user/mo) or above. Custom Objects are not available on Essential ($12) or Power ($29) tiers. We pre-create the destination schema including all custom fields and lookup relationships before any data import. If the destination account is on a lower tier, Custom Object records migrate as notes on the linked Person record with a flag for future schema migration when the account upgrades.

Regal's live integrations with Segment, HubSpot, Salesforce, Braze, and Iterable define which contacts are synced and how. We document the active integration endpoints, webhook URLs, API keys, and sync configuration during discovery. Reconnection to these platforms from Pipedrive is a post-migration configuration task performed by the customer's technical team or integration partner. We provide a written integration map listing each active Regal integration and its recommended Pipedrive equivalent (native integration, Zapier, Make, or custom API connection).

Regal supports branded caller ID (CNAM) configuration per campaign with carrier registration details and domain ownership records. These settings are tied to Regal's telephony infrastructure and cannot be exported. We export the carrier registration details, CNAM submission records, and domain ownership documentation as a reference file for the customer's admin to re-register with the destination telephony provider. The re-registration process is typically handled by the new telephony or SIP provider post-migration.

If the source Regal account uses a behavioral scoring model — where Journey interactions, event completions, and engagement frequency contribute to a contact score — that value migrates as a numeric custom field contact_score__c on the Pipedrive Person. The scoring algorithm itself (the weighting rules) is a Regal configuration that does not migrate; we document the raw score values as a data asset the customer's team can use to re-establish scoring logic in Pipedrive's automation layer or a connected enrichment tool.