Migrate from Regal.io to Zoho CRM

Regal Contacts map to Zoho CRM Contacts by default when a phone number and email are present. Contacts imported without an associated Account reference land as standalone Contact records; the customer chooses during scoping whether to create Zoho Accounts from Regal's company data or attach contacts to manually created Accounts. We preserve the Regal contactability status (contactable vs non-contactable) as a custom picklist field regal_contactability__c because Zoho does not enforce phone-number gating on record creation. Any Regal Contact missing both phone and email is flagged as a partial record and held in a reconciliation queue for the customer to resolve before import completes.

Regal's tenant-specific custom profile fields (Attributes) map to Zoho CRM custom fields on the Contact module. We extract the full attribute schema from Regal's API before migration, classify each attribute by Zoho field type (text, picklist, date, number, Boolean), and pre-create the custom fields in the destination Zoho CRM account via the Settings > Fields API before any data loads. Multi-select attribute values migrate to Zoho multi-select picklist fields.

Regal's behavioral event stream (call outcome, SMS sent, email opened, journey entry, journey exit, custom event) is the highest-volume data layer in the migration. We split by event type: call dispositions and call outcomes map to Zoho Tasks with TaskSubtype = Call and custom fields for duration and disposition code; meeting-related events map to Zoho Events; SMS and email interaction events map to Notes attached to the parent Contact; custom journey-trigger events map to a custom field journey_trigger_event__c on the Contact. We chunk the event export to avoid overwhelming the 300 req/sec Regal API rate limit and sequence event loads after Contact records are confirmed in Zoho so the parent lookup is satisfied.

Regal Campaigns (outbound programs with list selection, cadence, and goal definitions) map to Zoho CRM Campaigns. Campaign name, goal metrics, and member list transfer directly. Cadence logic (call and SMS frequency, time-of-day rules) is platform-specific and documented as a conditional rule list for the customer's admin to rebuild in Zoho Workflow Rules. We flag which Regal campaign lists are static vs dynamic so the admin knows whether to recreate them as Zoho static or dynamic campaign lists.

Regal Journeys are event-triggered conditional sequences of voice, SMS, and email steps with AI Agent routing. We do not migrate Journey logic as automation code because Zoho's Blueprint and Workflow Rule models are structurally different. We deliver a step-by-step Journey inventory document: for each active Journey, we list the trigger event, condition branches, step sequence (voice/SMS/email), agent handoff rules, and exit conditions. The customer's Zoho admin uses this document to rebuild Journeys as Zoho Workflow Rules (for field-update and email-alert triggers) and Blueprint stages (for process enforcement). Journey trigger conditions that reference Regal event types are mapped to the equivalent Zoho custom field values established during the event translation step.

Regal AI Agent scripts, decision trees, persona settings, and handoff logic are tied to Regal's proprietary agent runtime and cannot be exported via API or UI. We explicitly exclude AI Agent logic from migration scope. We do not attempt to reverse-engineer or approximate agent behavior in Zoho. We flag this limitation in the migration scope document and recommend the customer engage a Zoho conversational AI or telephony partner for agent rebuild post-migration.

Regal call transcripts are available as structured text associated with the Contact record. We export transcripts as plain text files and attach them to the parent Contact in Zoho CRM via the Notes module or as file attachments. Transcript availability depends on Regal's retention policy at the time of export; we validate transcript presence in the source export before loading. Call recording audio files are out of scope because they require media migration handling and Zoho CRM's attachment model is not optimized for large audio files.

SMS and email conversation history from Regal migrates as Zoho Notes attached to the Contact record. Thread chronology is preserved by sorting on timestamp. We flag that thread continuity in Zoho depends on the customer's Zoho email integration configuration; if the customer uses Zoho Mail or a connected email account, new emails sent after migration may not appear in the same thread context as the imported history. Thread metadata (message direction, delivery status) is stored in custom Note fields for reference.

Regal's branded caller ID configuration (carrier registration details and domain ownership records per campaign) is not transferable to Zoho CRM as a data record. We export the carrier registration details, phone number assignments, and CNAM disclosure records as a structured CSV for the customer to re-register with their telephony carrier or Zoho's telephony partner. Zoho CRM does not have a native CNAM management module; this is a carrier-side configuration step that the customer must complete post-migration.

Regal maintains live integrations with Segment, HubSpot, Salesforce, Braze, and Iterable that define which contacts are synced and how. We document each active integration endpoint, sync direction, field mapping, and trigger condition in a Zoho Integration Plan document. The customer's admin uses this plan to re-establish integrations via Zoho's native connectors (Zoho Flow, Zoho Sigma, or direct Zoho CRM API) post-migration. Segment and Braze integrations specifically require reconfiguration because Regal's event-stream model does not map directly to Zoho's batch-oriented data import approach.

Regal's contact owner (the user assigned to manage the contact) maps to Zoho CRM User by email match. We extract all distinct owner references from the Regal Contact export and match against the Zoho CRM User table. Any Regal owner without a matching Zoho User is held in a reconciliation queue; the customer provisions the missing User before record import resumes because Zoho's OwnerId field is required on most standard imports.

Regal tenants define custom event types beyond the standard call, SMS, and email events. These custom event schemas vary by tenant and are extracted as name-value property sets from the Regal event export. We classify each custom event type and map its properties to either existing Zoho CRM custom fields on Contact (if the properties are contact-level attributes) or a dedicated Zoho Custom Module (if the events represent transactional records with timestamps and multiple properties). The customer chooses the target during scoping.