Migrate from Regal.io to Nutshell

Regal Contacts map directly to Nutshell People. The mapping preserves firstName, lastName, phone, email, and all standard contact attributes. We extract the full Regal contact attribute schema during discovery and map each custom trait to a corresponding Nutshell custom field on the Person record. Note that Regal requires a phone number for a Contact to be reachable via campaigns and Journeys; Nutshell People records do not enforce this. We flag any Contacts in the source export that lack a phone number so the customer can decide whether to import them as non-contactable People records or exclude them from the initial load.

If the customer maintains Regal Campaign membership for prospects who have not yet been converted to marketing-qualified contacts, we offer a parallel Lead import. Campaign membership status and goal metrics from Regal become custom fields on the Nutshell Lead (e.g., campaign_name__c, campaign_goal__c). The split decision is made during scoping based on whether the customer wants to preserve a prospect pipeline in Nutshell separate from the contactable People records.

Regal Company records — typically synced from the customer's CRM or CDP via Regal's Segment, HubSpot, or Salesforce integration — map to Nutshell Company. The company name, domain, and address fields migrate directly. We resolve the Company-to-Person link using the email domain as the dedupe key during import, ensuring each Person record attaches to the correct Company.

Regal Custom Objects are defined by choosing one or more Custom Events as the source, with a unique identifier property. When migrating, we extract the full object schema — object name, event sources, identifier key, and property list — and map each property to a typed Nutshell custom field (Text, Long Text, Currency, or Date) on the entity the customer selects during scoping. Note that Regal's multi-contact-to-single-object relationship (e.g., co-borrowers sharing a mortgage) cannot reconstruct natively in Nutshell; we flag this as a manual consolidation step for the customer admin.

Regal Campaigns define outbound programs including list selection, cadence, and goal. We extract campaign membership and goal metrics (campaign name, status, assigned agent, goal type, and goal value) and attach them as custom fields on the Nutshell Lead or Person record. Cadence logic and list-refresh scheduling are platform-specific to Regal and do not transfer; we document these for manual rebuild in Nutshell Automations or as a spreadsheet for the sales ops team.

Regal call transcripts and outcome data migrate as Nutshell Notes attached to the corresponding Person record. The Note body contains the transcript text and disposition outcome. Audio recording files migrate as file attachments to the Note; audio availability is subject to Regal's retention settings at the time of export. Call duration and timestamp migrate to the Note's description field and to a custom field for reporting.

Regal conversational history for SMS and email threads re-associates with the migrated Nutshell Person record as Notes. Thread continuity in Nutshell is linear — there is no threaded inbox view equivalent to Regal's conversation model — so we append thread entries chronologically within a single Note per thread. The customer should be aware that thread context is preserved as text but the conversation experience in Nutshell differs from Regal's real-time messaging UI.

Regal's branded caller ID configuration (CNAM display name and carrier registration details) is telephony infrastructure that has no Nutshell equivalent, as Nutshell does not provide native outbound calling. We export the carrier registration details and domain ownership records as a configuration document so the customer can re-register with their carrier or CNAM provider independently. This item does not involve data migration but is flagged as a required manual step for teams relying on branded caller ID for answer rates.