Migrate from User.com to Salesforce Sales Cloud

User.com Contacts with lifecycle stage values below 'customer' (subscriber, lead, MQL) map to Salesforce Lead. Contacts at 'customer' or 'evangelist' map to Salesforce Contact attached to an Account. The split rule is computed during migration using User.com's lifecycle_stage property, and the original stage value is preserved in a custom field usercom_original_lifecycle__c on both Lead and Contact for audit and reporting. Web push subscribers, chat visitors, and FCM-key records that lack email or phone are flagged in the reconciliation report and only migrated if the customer explicitly opts in to avoid inflating Salesforce's storage footprint without business value.

User.com Company records map to Salesforce Account. The company name maps to Account Name and the domain attribute to Website. Account is created before Contact import so that the AccountId lookup is satisfied at Contact insert. Companies with no associated contacts are migrated as Accounts without Contacts and flagged in the reconciliation report for the customer to link manually or via a separate enrichment pass.

User.com Deals map to Salesforce Opportunity. Deal stage maps to Salesforce StageName using a stage-migration matrix defined during scoping. Owner (user_id on the deal) resolves to Salesforce OwnerId via email lookup against the destination User table. Closed-won and closed-lost reasons from User.com custom fields map to Opportunity custom fields for historical win/loss reporting.

User.com's deal stages are migrated to Salesforce StageName values within a single Sales Process (or a Record Type per pipeline if multiple deal pipelines are in use). Stage probability percentages are mapped from User.com stage weights to Salesforce StageProbability, rounded to Salesforce-allowed integers. Stage ordering is preserved so that pipeline velocity reports are accurate from day one.

User.com Events (calendar activities) map to Salesforce Event. StartDateTime, EndDateTime, Location, and description migrate directly. Attendees are migrated as EventRelation records linked to the migrated Lead, Contact, or Account. DateTime values export from User.com in ISO 8601 format and are normalized before insert to prevent timezone offset errors that occur when naive parsers treat the timestamp as local rather than UTC.

User.com Activities map to Salesforce Task. Email opens, chat sessions, and push notification events carry behavioral metadata that requires field-level mapping to Salesforce's Task schema. Status, Priority, and ActivityDate are preserved. Task.whoid points to the migrated Lead or Contact; Task.whatid points to the related Opportunity or Account. Some User.com activity types (push views, chat session durations) have no direct Salesforce equivalent and are stored in custom Task fields.

User.com custom fields on Contact, Company, and Deal migrate to Salesforce custom fields on Lead/Contact, Account, and Opportunity respectively. Choice and fixed-choice fields in User.com (exported with {} brackets) are mapped to Salesforce Picklist or Multi-Select Picklist fields with the corresponding values. Bool fields exported as 'f'/'t' are normalized to true/false during the transform step. The destination Salesforce custom fields are pre-created via metadata API before any data load to avoid import failures from missing field references.

User.com tags associated with contacts migrate to Salesforce Topics with TopicAssignment records, or to a multi-select picklist field on Contact if the customer prefers a simpler taxonomy. Tags associated with Deals migrate to a multi-select picklist field on Opportunity. The customer chooses the tag strategy during scoping. Tags used for segmentation (dynamic groups) are exported as static membership lists at migration time because dynamic re-evaluation must be recreated in Salesforce.

User.com Segments are dynamic groups based on contact attributes and behaviors. We export segment membership as static lists at migration time and deliver a written definition of each segment's criteria so the customer's admin can recreate the dynamic evaluation logic in Salesforce Reports, Campaigns, or a segmentation tool. Segments do not migrate as live-updating dynamic groups.

User.com Users referenced on Contacts, Companies, and Deals are resolved by email address against the Salesforce destination User table. Any User.com Owner without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive User.com owners can map to inactive Salesforce Users to preserve historical attribution.

User.com chat transcripts export bundled with contact records and must be flattened and re-associated. Each transcript thread becomes a series of Task records (one per message) linked to the migrated Contact, with custom fields for message direction (inbound/outbound), channel (chat), and timestamp. If the destination org includes Service Cloud, transcripts may map to Case comments instead.

User.com custom objects (Enterprise tier) migrate to Salesforce custom objects with the equivalent API name plus __c suffix. We pre-create the destination schema including all custom fields, lookup relationships to standard and custom objects, and validation rules before any data import. Custom object migration runs last because they frequently have foreign-key references to migrated standard objects.