Migrate your Rule data

Rule contact profiles include standard fields (name, email, phone) plus behavioral attributes and channel preferences. We map these 1:1 to destination CRM contact objects and preserve custom field values as custom properties in the target.

Account-level data in Rule ties to contact records via a parent relationship. Where the destination CRM uses a different account schema, we map the account name and domain field and flag any mismatched company-to-contact cardinality.

Rule segments are dynamic filter-based lists. We export segment definitions as filter logic rather than snapshots, and reconstruct the same segment rules in the destination CRM if it supports dynamic lists.

Workflows contain trigger conditions, time delays, and channel actions. We map trigger types (event-based, date-based, tag-based) and action sequences, noting that complex multi-branch workflows may require manual recreation in the destination.

Campaigns in Rule group related automations and track aggregate performance metrics. We export campaign metadata and linked contact counts, but engagement analytics are time-bound and may not replay in full in the destination.

Contacts can carry multiple tags in Rule. We preserve all tag assignments per contact and map them to the destination CRM's tag or label field directly.

Open, click, bounce, and unsubscribe events are logged per contact. We export the event log as a historical record; whether the destination CRM surfaces this history in its UI depends on the platform's data model.

Channel-specific engagement events are tracked separately from email events. We export these as activity records and map them to the destination CRM's activity or engagement log objects.

Custom fields on contacts and companies may include dropdown, date, numeric, or text types. We map field types and preserve option lists; multi-select fields require explicit mapping to the destination field type.

Email and SMS templates exist as reusable content assets. We export template body text and subject lines; images and dynamic variable syntax may need reformatting depending on the destination's template engine.

Where Rule includes a sales pipeline view, stage names and order are exported as configuration metadata and recreated as pipeline stages in the destination CRM.

Rule user accounts include name, email, and role. We map owner assignments on contacts and deals to corresponding users in the destination system; unresolvable users are flagged for reassignment.

File attachments linked to contacts or campaigns are exported via Rule's file API. We download and re-upload to the destination, preserving original filenames and attaching to the corresponding record.

Suppressed contacts (unsubscribed, bounced, blocked) are exported as a suppression list. We flag these records in the destination to prevent re-import into active marketing lists.