Migrate from Resulticks to Salesforce Sales Cloud

Resulticks Contacts migrate to Salesforce Contact records with all standard fields (Name, Email, Phone, Address) mapped directly. Custom Contact properties from Resulticks inspect during scoping and map to typed Salesforce custom fields (Text, Number, Picklist, Date, Checkbox). Email is the dedupe key. Owner assignment resolves by email match to Salesforce User.

Resulticks Contacts with a prospect lifecycle status that the customer designates as unqualified can be split to Salesforce Lead. We apply the split rule defined during scoping (e.g., all Contacts with lifecycle_stage = Subscriber or Lead map to Lead; Customer and Evangelist map to Contact). The split is computed during the transform phase, and the original Resulticks lifecycle_stage is preserved in a custom field resulticks_lifecycle__c on both Lead and Contact.

Resulticks Audience definitions (filter conditions on Contact attributes and event behaviors) do not export as reusable segments. We preserve membership by exporting the Contact IDs within each Audience and creating Salesforce Campaigns with those Contact IDs as CampaignMembers. For dynamic segments, we deliver a written filter definition document so the customer can rebuild equivalent Campaign inclusion rules or Data Cloud segments in Salesforce.

Resulticks Tags at the Contact level migrate as Salesforce Contact Tags (native tag functionality) and optionally as a multi-select picklist custom field resulticks_tags__c. Tag distribution per Contact is preserved. The customer chooses between tags and a custom field during scoping based on reporting needs.

Resulticks Campaign metadata (name, status, channel assignment, start and end dates) migrates to Salesforce Campaign. Campaign content assets, email body copy, and creative files do not export from Resulticks and are flagged for manual transfer or rebuild in Salesforce Marketing Cloud or a content DAM.

Resulticks custom Contact properties vary by account configuration and may include legacy field types, multi-select values, or computed date fields. We inspect the full field schema during scoping, map each property to a compatible Salesforce field type (Text, Number, Picklist, Date, Boolean), and pre-create the custom fields in the destination org before import. Fields that have no compatible Salesforce type are flagged for review.

Resulticks event history (page views, email opens, purchase events, custom track events) migrates to a custom Event_History__c object with ContactId lookup, event_type, event_date, and JSON payload fields for custom event properties. Due to schema variability and volume, we migrate a configurable event window (default 12 months) and normalize event_type to a picklist. The customer can expand the window during scoping.

Resulticks platform users map to Salesforce User records by email match. Role and permission assignments are documented during scoping and the customer configures Salesforce profiles and permission sets post-migration. Users without a matching Salesforce User are held in a reconciliation queue for admin provisioning.

Resulticks email engagement records migrate to Salesforce EmailMessage (content) linked to a Task (activity timeline entry). WhoId points to the migrated Contact or Lead; WhatId points to the related Campaign or Account. Email body and subject migrate as Salesforce-compatible rich text.

Resulticks call engagement records map to Salesforce Task with TaskSubtype = Call. Call duration, disposition, and recording URL (if accessible) migrate to custom Task fields. ActivityDate is set to the original Resulticks timestamp to preserve timeline ordering.

Resulticks meeting records map to Salesforce Event with StartDateTime, EndDateTime, Subject, and Location preserved. Attendees map to EventRelation records linked to the migrated Contact, Lead, or User records.

Resulticks task engagements map to Salesforce Task with Status, Priority, Subject, and ActivityDate preserved. Owner assignment resolves by email match to Salesforce User. Task content migrates as the Task Description field.

Resulticks Journey flows store branching conditions, wait steps, AI-driven decision nodes, and multi-channel node sequences in a proprietary format that cannot be exported. We photograph and document the full Journey map during discovery and deliver a written Journey reference document with screen captures, node logic, and recommended Salesforce Flow equivalents. The customer or a Salesforce partner rebuilds the flows post-migration.

Resulticks Genie AI-driven audience recommendations and automated segmentation logic do not export. We document the Genie rule definitions and segment outputs observed during the discovery phase and deliver a written Genie replacement guide recommending equivalent Salesforce Reports, Campaign Lists, or Data Cloud segment configurations.