Migrate from Rule to HubSpot

Rule contacts migrate as HubSpot Contacts. Primary company resolves to a HubSpot Company record via domain match or explicit company field. All standard contact properties (name, email, phone, jobtitle) map directly. Rule engagement tags and custom properties migrate as HubSpot custom properties.

Rule segment tags indicating engagement status (e.g., 'active subscriber', 'marketing qualified') translate to HubSpot lifecycle_stage values. Mapping depends on Rule's tag taxonomy — we deliver a tag-to-stage mapping plan before migration runs. The mapping plan includes a table listing each Rule tag, its corresponding HubSpot lifecycle_stage value, and any business logic applied (e.g., defaulting unknown tags to 'subscriber'). This ensures your team can validate the translation before data moves.

Rule company records migrate as HubSpot Company objects. Company name, domain, industry, employee count, and annual revenue map to HubSpot's standard Company properties. Parent-company hierarchies in Rule translate to HubSpot's parent-company association. If a Rule company lacks a domain, we use the company name as the primary identifier and create a placeholder domain for HubSpot compatibility. All custom company properties also migrate as HubSpot custom properties.

Rule deals migrate as HubSpot Deals. Deal name, amount, stage, and close date map to HubSpot Deal properties. If Rule uses a single deal stage model, we map it to a HubSpot pipeline and stage picklist. Multi-stage Rule deals map to multiple HubSpot pipeline stages.

Rule deal pipelines map 1:1 to HubSpot Deal pipelines. Stage names map to HubSpot stage values within each pipeline. Stage probability re-applied from HubSpot's stage defaults unless your team specifies custom probabilities. If Rule includes stage-specific win/loss notes, those are preserved as custom deal properties in HubSpot to maintain historical context. Your team can later adjust probabilities and forecast categories in HubSpot's pipeline settings.

Rule email opens, clicks, and bounces migrate as HubSpot engagement activities logged against the Contact record. Original timestamps preserved. Bounce events migrate as a custom property update rather than a standard activity type. For each email event, the activity type, timestamp, and campaign source are stored in custom fields, allowing you to build reports on open rates, click-through rates, and bounce patterns within HubSpot's analytics suite.

Rule SMS and RCS engagement events (sends, replies, opt-outs) have no native HubSpot equivalent. We log them as custom activity records with the original timestamp and engagement type preserved in custom fields on the Contact. These custom activity entries enable you to track SMS response rates and RCS interactions within HubSpot, though they appear in custom reports rather than the native engagement timeline.

Rule trigger-based workflows and customer journeys do not export in a transferable format. We deliver a Workflow Rebuild Reference export documenting Rule's trigger conditions, audience filters, and action steps so your HubSpot admin can reconstruct the logic in HubSpot workflows and sequences.

Rule campaigns and customer journeys aggregate contacts by audience segment and channel. We map campaign membership to HubSpot static or dynamic lists and preserve campaign names for list labeling. Channel-specific journey steps are documented for rebuild as HubSpot workflows. This translation ensures that audience segments remain intact in HubSpot, allowing you to reuse existing campaign logic when designing new HubSpot workflows and automated sequences.

Rule custom contact properties migrate as HubSpot custom properties on the Contact object. Property type (text, number, date, picklist) maps to the equivalent HubSpot field type. Picklist value mapping is done value-by-value where the picklist options differ between platforms. For multi-select picklists, each selected value is stored as a separate entry in HubSpot's multi-checkbox field, preserving the original multi-value nature of the Rule property.

Rule file attachments on contacts, companies, or deals are downloaded and re-uploaded to HubSpot Files. Files are associated to the corresponding HubSpot record. File size limits (HubSpot default 25MB per file) apply — large files flagged for pre-migration review. During re-upload, file metadata such as original upload date and author is preserved in HubSpot's file details, and any file exceeding the 25MB threshold is noted in the migration plan for manual handling or compression before import.