Migrate from Regal.io to Freshsales

Regal Contacts map to Freshsales Lead if the contact is pre-qualified only (no active deal association) or if phone number is present but no campaign eligibility flag is set. Contacts with campaign membership and Journey enrollment map to Freshsales Contact tied to an Account. We compute the split using Regal's contactability status and campaign_enrollment flags during extraction. The original Regal contact_id is preserved in a custom field regal_original_id__c for audit and cross-referencing.

Regal Contact Attributes (custom profile fields per tenant) are extracted from the full attribute schema before migration. Each attribute is mapped to a Freshsales custom field of equivalent type: string to text, number to number, boolean to checkbox, date to date. Multi-value attributes (e.g., campaign_tags) map to Freshsales multi-select picklist. We pre-create all custom fields in Freshsales before record import begins.

Regal Events are behavioral records (call outcome, SMS sent, email opened, Journey step triggered) attached to a Contact. Because Freshsales does not have a native event-stream object, we transform Events into Activity records: call outcome Events become Tasks with TaskSubtype=Call and disposition preserved; SMS and email Events become Notes attached to the Contact or Lead. The original event_type and event_properties are stored as JSON in a custom text field event_payload__c for audit.

Regal Campaigns define outbound programs with list selection, cadence, and goals. We map campaign membership and campaign status to Freshsales custom fields on Lead and Contact (campaign_name__c, campaign_status__c). Campaign goal metrics (target contacts, connected calls) are documented as text notes for manual entry in Freshsales reporting. Cadence and list-refresh logic is platform-specific and does not transfer.

Regal Custom Objects (Opportunities, Appointments, Quotes, Loan Applications, etc.) map to Freshsales custom objects of equivalent API name. We pre-create the destination schema in Freshsales including all custom fields, lookup relationships to Contact or Account, and any validation rules. The mapping of Custom Event triggers to Custom Object record updates is documented as a step-by-step configuration guide for the customer's Freshsales admin to rebuild.

Regal call transcripts are exported as structured text and attached as Freshsales Notes linked to the Contact or Lead. We map call disposition, duration (in seconds), and recording availability (flagged if unavailable due to Regal retention policy) to Note custom fields. Audio file availability is confirmed with Regal at extraction time; if recordings are unavailable, we document this gap in the migration report.

Regal SMS conversational history is associated with Contact records. We extract thread-level data (direction, content, timestamp) and reattach it to the Freshsales Contact as a series of timestamped Notes with a sms_thread__c flag. Thread continuity in Freshsales depends on the CRM's activity rendering; we document the expected display behavior so the customer's team knows what to expect.

Regal AI Agent configurations (voice scripts, decision trees, persona settings) are tied to Regal's proprietary agent runtime and cannot be exported via API or UI. We explicitly exclude Agent logic from migration scope and flag it for manual rebuild. We do migrate conversation outcome data and Journey trigger conditions so business context is preserved even if agent logic must be recreated. Freshsales Freddy AI is a separate assistant feature, not a direct replacement for Regal's agent runtime.

Regal Journeys are conditional, event-triggered sequences of voice, SMS, and email steps built in a no-code Journey Builder. We document Journey logic as step-by-step conditional rules (trigger event, conditions, action sequence) in a written inventory so the customer's admin can reconstruct them in Freshsales CRM workflows or a separate automation tool. Freshsales Workflows are property-triggered but do not support the same event-stream model that drives Regal Journeys.

Regal branded caller ID (CNAM) configuration is carrier-specific and tied to Regal's telephony infrastructure. We export the carrier registration details and domain ownership records as a text document for the customer's IT team to re-register in the destination telephony platform. Freshsales CRM does not have native branded caller ID; the customer will need a third-party voice provider (Freshsales CRM Voice or an alternative like Aircall, Dialpad, or Twilio) to re-establish CNAM.