Migrate from Regal.io to HubSpot

Regal contacts map directly to HubSpot contacts. The primary company_name attribute is resolved against HubSpot company records by domain match or manual mapping, then linked via the Contact's Associated Company field. Any missing company associations are logged for manual review before the final import to avoid orphaned contacts.

Regal standard attributes like first_name, last_name, email, phone, and job_title map to HubSpot's native Contact Properties with the same names. These require no transformation. FlitStack validates each value against HubSpot's property type constraints, ensuring that phone numbers are formatted correctly and email addresses meet RFC standards before import.

Regal custom Contact Attributes (defined per workspace) are created as HubSpot custom properties on the Contact object before import. Data type matching (text, number, date, picklist) is done per attribute during the mapping phase. For picklist attributes, FlitStack maps each Regal value to the corresponding HubSpot picklist option, creating new options if they do not already exist in HubSpot's property definition.

Regal call events become HubSpot engagement log entries of type 'Call' on the Contact timeline. Properties like call_duration, outcome, and recording_url map to custom properties on the engagement record. FlitStack also records the original call start time as a custom datetime property, preserving the exact timestamp for reporting and historical analysis.

Regal SMS events are logged as HubSpot engagement entries on the Contact timeline. The SMS body text is preserved in a custom property, with direction (inbound/outbound) mapped from Regal's sms_direction field. If the SMS direction is not recognized, FlitStack flags the record for review and defaults to 'outbound' to maintain data consistency.

Regal custom Event Types (behavioral events beyond call and SMS) map to HubSpot Custom Behavioral Events. Event Properties are stored as custom event properties in HubSpot's event schema. FlitStack creates a custom event definition in HubSpot for each unique Regal event type, mapping all associated event properties to the corresponding custom fields within the event schema.

Regal stores company as a text attribute on Contact. Unique company_name values are extracted, deduplicated, and imported as HubSpot Company records. Domain and industry are mapped from Regal company attributes where present. If multiple contacts share the same company name but lack a domain, FlitStack generates a list of potential duplicates for your team to merge manually before final import.

Regal stores call recordings as hosted URLs in the recording_url event property. FlitStack fetches each recording and re-uploads it as a HubSpot File attached to the relevant Contact record's timeline. During this step, FlitStack verifies the file size and format, converting any non‑standard audio codecs to MP3 to ensure compatibility with HubSpot's file viewer.

Regal agent IDs and owner assignments are resolved by email match against HubSpot Users. Unmatched agents are flagged for team assignment before the migration runs so no contact lands without a HubSpot owner. If a HubSpot User does not exist for a matched email, FlitStack creates a placeholder user and assigns those contacts temporarily, allowing your admin to reassign ownership post‑migration.

Regal's Journey Builder configurations (triggers, branching logic, outbound sequences) are not data — they are platform configuration with no HubSpot equivalent. FlitStack exports journey definitions as documentation for the HubSpot admin to rebuild in HubSpot workflows. The exported documentation includes each trigger condition, decision branches, and action steps, providing a clear blueprint for recreating the logic in HubSpot's workflow editor.

Regal SMS templates and branded caller configurations are platform-specific settings that do not export as data. These are surfaced in the migration documentation as items requiring manual rebuild in HubSpot's tools. The documentation lists each template's variables, conditional logic, and fallback routes, enabling your team to replicate the same communication flows using HubSpot's sequence and workflow features.