Migrate from Rule to Freshsales

Rule contact profiles map to Freshsales Lead or Contact depending on lifecycle stage. We use Rule's lifecycle stage property as the split criterion: contacts in early stages (subscriber, lead) become Freshsales Leads; contacts in qualified stages (MQL, SQL, customer) become Freshsales Contacts tied to an Account. The original Rule lifecycle stage is preserved in a custom field rule_lifecycle_stage__c on both Lead and Contact for audit. Rule behavioral attributes (engagement scores, channel preferences) map to Freshsales custom fields or are documented as new fields to create before migration.

Rule account-level data maps directly to Freshsales Account. The account name and domain fields map to Account Name and Website. Rule company records tied to contacts via parent relationship are resolved before Account import so that Contact.AccountId is satisfied at insert time. Any Rule company without a contact association is imported as a standalone Account and flagged for the customer to review.

Rule deals map to Freshsales Deals. The Rule deal stage maps to Freshsales Deal Stage, and Rule pipeline assignments map to Freshsales pipeline or deal track configuration. Closed-Lost and Closed-Won reasons from Rule become Freshsales Deal Loss Reasons if configured. We create the pipeline and stage configuration in Freshsales before migration using Rule's pipeline metadata.

Rule tags on contacts migrate to Freshsales Tags. Freshsales stores tags as a native Tagging feature on Contacts, Leads, Accounts, and Deals. Each Rule tag is created as a Freshsales tag and linked to the migrated record. Multi-tag assignments per contact are preserved as multiple tag links.

Rule custom fields on contacts and companies map to Freshsales custom fields on the corresponding object (Lead, Contact, Account, Deal). Dropdown, date, numeric, and text field types map directly. Multi-select fields require explicit mapping because Freshsales custom fields use single-select or multi-select picklist types. During lead conversion, Freshsales allows per-field mapping from Lead custom fields to Contact, Account, and Deal custom fields; we document this mapping and apply it as a pre-validated configuration step.

Rule email open, click, bounce, and unsubscribe events export as engagement log entries. We map these to Freshsales Task records with type = Email. Each activity record is linked to the parent Contact or Lead via WhoId. Bounce and unsubscribe events are annotated with a rule_event_type__c field set to Bounce or Unsubscribe so that Freshsales lifecycle stage can be updated accordingly during migration.

Rule SMS, RCS, and social channel engagement events export as channel-specific logs. Freshsales does not have native SMS, RCS, or social activity types separate from Task, so we map these to Task records annotated with a rule_channel__c field (SMS, RCS, or Social) and a rule_event_detail__c field carrying the original engagement event data. This preserves the full engagement history in Freshsales without creating orphaned records.

Rule automation workflows contain trigger conditions, time delays, and channel actions. We do not migrate workflows as code because Rule's event-driven journey builder and Freshsales's trigger-condition-action model are structurally different. We export every active Rule workflow definition (triggers, conditions, actions, and contact segments) and deliver it as a written inventory document with a recommended Freshsales workflow equivalent. The customer's admin rebuilds workflows in Freshsales using the inventory as a reference. Workflows that reference deleted or archived contacts are flagged as orphaned and removed from the inventory before handoff.