Migrate your User.com data

The primary object in User.com. Any record with an email, phone, user_id, last_heard, web push subscription, or FCM key qualifies as a contact and is counted for billing. We migrate all standard contact fields and preserve custom properties during import.

Companies are linked to contacts and can be imported via CSV or API. We preserve the company-contact association and all standard company attributes.

Deals have their own CSV import path and API endpoint. We map deal stages, values, owners, and custom deal fields to the destination structure. Deals can also carry a custom user_id for cross-object reference.

Events (calendar/activity events) are importable via CSV. We preserve event timestamps, attendees, and event-type attributes. DateTime values export in ISO 8601 format which we normalize during mapping.

Activities are importable via CSV. The schema is straightforward but some activity types (email opens, chat sessions, push notifications) have behavioral metadata that requires field-level mapping to match destination conventions.

User.com supports custom fields on all major objects. We export the full custom property schema and map values, but destination platforms may require custom field recreation. Choice and fixed-choice field export formats changed from [] to {} — we normalize this.

Tags are associated with contacts and deals. We preserve tag assignments during migration. Some destination CRMs treat tags differently (as labels, segments, or lists) so mapping rules apply.

Segments in User.com are dynamic groups based on contact attributes and behaviors. We export segment definitions and membership at migration time, but dynamic re-evaluation must be recreated in the destination platform.

User.com's automation and workflow logic is not exported through standard CSV or documented API endpoints. We do not migrate automations. Customers must rebuild automation sequences manually in the destination platform or use the destination's native migration tooling.

Chat transcripts and conversation history can be exported. However, the exported format bundles conversation threads with contact records, requiring us to flatten and re-associate threads to contacts at the destination. Push subscription records trigger the billing flag on import.

Email templates and campaign history are not accessible via documented export endpoints. We do not migrate email templates or campaign records. Campaign performance metrics must be recreated or referenced externally.

Web push subscribers count as contacts for billing purposes. During migration scoping we explicitly flag which records should not land as push-active in the destination to avoid unexpected contact-count inflation.