Migrate from User.com to Freshsales

User.com Contacts map to Freshsales Lead or Contact based on engagement profile. Records with an email and no deal association and no recorded engagement events map to Freshsales Lead. Records with a deal association, recorded calls, emails, or meetings map to Contact attached to an Account. We evaluate the contact's deal_count, last_event_type, and tags during migration to assign the correct destination model. The original User.com contact_id is preserved in a custom field usercom_original_id__c for audit and cross-reference.

User.com Company records map to Freshsales Account. The company name maps to Account Name; the domain maps to Website. Freshsales performs duplicate detection on Account Name and Website during import. We resolve the company-contact association at migration time so that each Contact imported after its parent Account has the AccountId lookup satisfied. All standard company fields (address, city, country, industry, phone) map to Freshsales Account standard fields; custom company properties map to Freshsales custom Account fields.

User.com Deals map to Freshsales Opportunity. The deal title becomes Opportunity Name, deal_value maps to Amount, deal_stage maps to Pipeline Stage, and owner maps to Owner (resolved by email match against Freshsales User). We create Freshsales Pipeline and Stage entries that correspond to the User.com pipeline configuration before import. Custom deal fields map to Freshsales custom Opportunity fields. The closed_lost_reason and closed_won_reason from User.com custom properties migrate to Freshsales custom fields on Opportunity.

Each User.com pipeline's stage values migrate to Freshsales Pipeline and StageName entries. We create the Freshsales Pipeline first, then add Stage entries with matching names and probabilities. Probability percentages from User.com round to the nearest integer. Stage display order is preserved from User.com. If User.com has multiple pipelines, we create a corresponding Freshsales Sales Process per pipeline.

User.com Events (calendar events with start time, end time, title, description, location, and attendees) map to Freshsales Task records. Start time and end time from User.com become Task Due Date and Activity Date; the title becomes Subject. Event attendees resolve to Freshsales User lookups where email matches exist; unresolved attendees are noted in the migration report. We import events before contacts so that the WhoId (Contact or Lead reference) is available at import time.

User.com Activities include email opens, email clicks, call logs, and push notification records. Each activity type maps to a typed Freshsales Task or EmailMessage. Call activities become Task with TaskSubtype = Call and duration preserved. Email engagement activities (opens, clicks) become Task with a custom type field. All activities link to the parent Contact or Lead via WhoId. The original User.com activity timestamp becomes Activity Date to preserve timeline ordering.

User.com tags (stored as string arrays on contact and deal records) migrate to Freshsales Contact Type field. For single-tag use cases we use Freshsales' built-in Contact Type field. For multi-tag scenarios we create a Freshsales multi-select custom field. Tag values transfer verbatim; we flag any tag value longer than 40 characters for truncation review before import.

User.com dynamic segments (auto-populated based on contact attribute filters) do not reproduce as dynamic in Freshsales because Freshsales filters are evaluated at query time, not stored as segment definitions. We export segment membership as a static list of contact identifiers at migration time and create Freshsales contact lists with the same names. The customer rebuilds the dynamic filter logic in Freshsales using Freshsales Filters. Segment definitions are documented in the handoff inventory.

User.com custom properties on Contact, Company, and Deal migrate to Freshsales custom fields. Choice fields require pre-creation in Freshsales before value import; we create the custom field definition first, then import values. Bool properties migrate to Freshsales Checkbox fields with f/t normalization applied. Date properties use ISO 8601 format compatible with Freshsales date field import. JSON-encoded properties in User.com export require parsing and field extraction before mapping to Freshsales field types.

User.com Owners map to Freshsales User records by email match. We extract all owner_email values referenced on Contact, Company, Deal, and Activity records and match against the Freshsales User table. Owners without a matching Freshsales User enter a reconciliation queue for the customer's admin to provision before the migration resumes. Assigned records from unresolved owners default to the migration admin user during the import phase and are reassigned post-provisioning.

User.com chat transcripts and conversation history export as bundled data with contact records. We extract conversation threads, flatten them to a readable text format, and import as Freshsales Note records linked to the parent Contact or Lead via ContentDocumentLink. Chat message timestamps map to Note Created Date for chronological ordering. The chat_session_id is preserved in a custom field on the Note for audit. Native Freshsales chat functionality (Freshchat integration) is not migrated as part of the conversation history import.