Migrate from User.com to Pipedrive

User.com Contacts map directly to Pipedrive People. The primary mapping challenge is identifying which User.com records carry billing-triggering attributes (email, phone, chat last_heard, push subscription, FCM key) so that the customer understands the contact-count impact before Pipedrive import begins. We preserve all standard contact attributes and custom properties, but note that Pipedrive People do not have a native marketing-subscription flag equivalent; email opt-out status migrates to the HasOptedOutOfEmail field if present in the User.com export.

User.com Company records map to Pipedrive Organizations. The company-contact association migrates by linking each Person record to its parent Organization via the Organization's unique ID. Pipedrive's Organization is a flat record with no hierarchical account structure at Lite; multiple Organizations can be linked manually if the customer's User.com data has hierarchical company relationships.

User.com Deals map to Pipedrive Deals. The critical mapping is deal stage: User.com stage IDs must be translated to Pipedrive stage IDs within a specific pipeline. User.com's documentation specifies that pipeline and stage must be provided as IDs during import, not names, and that stage IDs vary per pipeline. We pre-create Pipedrive pipelines and stages matching the User.com structure, extract the correct IDs via the Pipedrive API, and map them during the transform phase before CSV generation.

Each User.com pipeline with its stages maps to a Pipedrive Pipeline with corresponding Stages. User.com requires that pipeline and stage IDs are provided as integer pairs during import. We configure the Pipedrive pipeline structure first, extract stage IDs via API, and use those IDs as the foreign key values in the Deal import CSV. Status values in User.com Deals must be provided as integers: 1=In progress, 2=Won, 3=Lost, 4=Archived.

User.com Event records (calendar/activity events) map to Pipedrive Activities of type Meeting. We preserve event timestamps, attendee lists, and event-type attributes. DateTime values export from User.com in ISO 8601 format, which Pipedrive accepts directly. Attendees resolve to Pipedrive Person or Organization records by email match.

User.com Activities map to Pipedrive Activities. The activity type must be provided as an integer in User.com's import: 1=Call, 2=Email, 3=Meeting, 4=Task, 5=Lunch, 6=Deadline. Custom activity types (non-standard types not in User.com's defaults) must be pre-created in User.com before export with their integer IDs; otherwise, custom type data is lost. We flag this during scoping and advise customers to pre-create custom types or accept partial loss.

User.com custom properties on Contacts, Companies, and Deals migrate to Pipedrive custom fields. We export the full custom property schema, including field types, and recreate them in Pipedrive before import. Pipedrive field types must match the data: text to text, number to number, date to date, choice to drop-down. Choice and fixed-choice fields in User.com use {} bracket notation in exports; we normalize these to comma-separated values or JSON arrays that Pipedrive's importer accepts.

User.com Tags migrate to Pipedrive Labels on the corresponding Person, Organization, or Deal record. Labels are flat key-value tags in Pipedrive with no hierarchical structure. We preserve all tag assignments. Note that Pipedrive Labels behave differently from User.com Segments (which are dynamic and behavior-based); we flag which tags originated as Segments so the customer knows these require manual rebuild as Pipedrive Filters or Lists.

User.com Segments are dynamic groups defined by contact attributes and behaviors that re-evaluate in real time. We export the segment definition (rules, conditions, operators) as a written record, but the dynamic membership cannot be preserved as a static group in Pipedrive. The customer must rebuild Segments as Pipedrive Filters (for static lists) or as Smart Lists (Growth plan and above) post-migration. We deliver a segment-to-filter mapping document as part of the handoff.

User.com chat transcripts can be exported but bundle conversation threads with contact records. We flatten the conversation history and re-associate each message to the correct Person record as a Note with a timestamp. Pipedrive Notes support rich text, which preserves message formatting. The chat metadata (agent name, channel) migrates as Note custom fields. Note that Pipedrive does not have a native conversation threading model; chat history appears as a chronological note stream rather than a threaded inbox.

User.com automation sequences are not accessible via documented CSV export or public API endpoints. We explicitly exclude automation migration from scope and do not rebuild them. We deliver a written inventory of every active User.com automation with its trigger, conditions, delays, and actions, plus a recommended Pipedrive workflow equivalent (Automation rules, Workflow automation, or Goals). The customer's admin rebuilds these post-migration.

Email templates and campaign performance records (open rates, click rates, send history) are not available via documented export endpoints in User.com. We do not migrate these objects. Customers with significant template libraries should take screenshots or export PDFs of active templates before migration begins. Campaign performance data should be exported to a BI tool. Pipedrive Email Templates are rebuildable manually; the customer or a Pipedrive implementation partner recreates them post-migration.