Migrate from Rule to Nutshell

Rule Contact records with lifecycle stage indicating an unqualified prospect (subscriber, lead, marketing-qualified) map to Nutshell Lead. Contacts with a lifecycle stage of customer or evangelist map to Nutshell People. We compute the split during scoping using Rule's lifecycle_stage property and preserve the original value in a custom field on both Nutshell Lead and People records for audit continuity.

Rule Account records map directly to Nutshell Account. Rule's account name, domain, and address fields map to Account name, website, and address fields. Account is imported before People records so that the Account lookup relationship is satisfied at the moment of People insert.

Rule Deal records map to Nutshell Deal. Rule's deal stage maps to Nutshell pipeline stage, deal value maps to Amount, and associated contacts and accounts resolve to the corresponding Nutshell People and Account records via email and name matching.

Rule Segments are dynamic filter-based lists. We export segment definitions as filter logic rather than point-in-time snapshots and recreate them as Nutshell People Lists where Nutshell's filtering supports equivalent conditions. Static exports are migrated as a saved List with the segment name retained.

Rule automation workflows with trigger conditions, time delays, and channel actions are documented as a written inventory. We export workflow names, trigger types (event-based, date-based, tag-based), action sequences, and linked contact counts. Nutshell's automation rules (Pro+ tier) use a different trigger model; the customer's admin rebuilds the equivalent logic post-migration.

Rule Campaigns group related automations and track aggregate performance metrics. We export campaign metadata (name, status, linked contact counts) and channel assignments. Engagement analytics (opens, clicks, revenue attribution) are time-bound to the campaign window and do not replay in Nutshell's campaign model; we include the aggregate metrics as a reference note on the migrated campaign record.

Rule tags on Contacts migrate to Nutshell Tags applied to the corresponding People or Lead record. Tag assignments are preserved per contact so that segmentation logic can be reconstructed using Nutshell's tag-based filters in Lists and automation rules.

Rule email open, click, bounce, and unsubscribe events export as activity records. We map these to Nutshell Activity entries on the corresponding People or Lead record, annotating each entry with the event type and timestamp. Nutshell surfaces these on the People activity timeline.

Channel-specific engagement events from SMS, RCS, and social channels are exported from Rule as separate channel logs. We consolidate these into Nutshell Activity records annotated with the source channel (e.g., SMS, RCS, Social) in the activity description or a custom field, since Nutshell does not have native multi-channel engagement type fields.

Rule custom fields on Contacts and Companies (dropdown, date, numeric, text, or multi-select types) are mapped to Nutshell custom fields of the equivalent type on People, Account, or Lead objects. Multi-select fields from Rule require explicit mapping to Nutshell's multi-select field type. Field options are preserved for dropdown fields; free-text fields migrate values as-is.

Rule user accounts (name, email, role) map to Nutshell Users. We resolve owner assignments on Deals and Contacts by matching Rule owner email to Nutshell user email. Any Rule owner without a matching Nutshell user is flagged for admin provisioning before record import begins.

Rule suppressed contacts (unsubscribed, bounced, blocked) are exported as a separate dataset. We apply a suppressed status flag to each corresponding Nutshell People record. If the customer has a marketing email tool connected to Nutshell, we also create a suppression list in that tool where supported.