Migrate from User.com to HubSpot

User.com users map to HubSpot contacts. Email, phone, name, and address fields translate directly. If the User.com record has no email, it lands as an incomplete HubSpot contact and your team completes the record post-migration. Original User.com create dates are preserved as a custom datetime property.

Any User.com custom field on a user record becomes a HubSpot custom contact property. We create the property in HubSpot before import using the same field type (text, number, date, dropdown). Multi-select or fixed-choice fields from User.com become HubSpot dropdown or multi-checkbox properties with values preserved.

User.com companies map directly to HubSpot companies. HubSpot requires a domain value for company identification; if User.com company records lack a domain, we use a placeholder domain and flag those records for post-migration enrichment. Parent-company hierarchies map to HubSpot's parent company field.

User.com deals map to HubSpot deals. Deal name, amount, close date, owner, and pipeline stage transfer directly. Each User.com deal pipeline becomes a HubSpot deal pipeline with stage values preserved as pick-list options. We validate that stage values do not exceed HubSpot's 200-character limit before import.

User.com pipeline names become HubSpot deal pipeline names. If a User.com deal has no pipeline assigned, we assign it to HubSpot's default pipeline and flag the record for pipeline assignment review. Pipeline names longer than 60 characters are truncated to fit HubSpot's pipeline name limit, and stage values exceeding 200 characters are flagged for manual review before import.

User.com has no native lifecycle_stage equivalent. Any status, stage, or lifecycle field used in User.com migrates as a HubSpot custom property (custom_field_required). Post-migration, your team maps this field's values to HubSpot's built-in lifecycle_stage pick-list, enabling HubSpot's marketing-centric reporting and lead routing.

User.com events (calls, emails, meetings) map to HubSpot engagements. Calls and emails become HubSpot Tasks with the engagement type recorded in a custom property. Meetings become HubSpot Meetings (Calendar events). Original timestamps and owner assignments are preserved on all engagement records.

User.com notes migrate as HubSpot engagement notes. We preserve note body content, original create timestamps, and owner links. Rich-text formatting in User.com notes converts to HubSpot's note format. Note attachments are downloaded and re-uploaded to HubSpot's file storage, with each file linked back to its parent contact, company, or deal record. Any notes exceeding HubSpot's body length limit are flagged for manual review.

User.com sequences and automations have no equivalent in HubSpot's object model — they are not data records but behavioral logic. We export all sequence definitions (step order, delay rules, enrollment triggers) as a structured JSON and CSV reference package. Your HubSpot admin rebuilds sequences using HubSpot's built-in workflow and sequence tools.

User.com file attachments on users, companies, or deals are downloaded and re-uploaded to HubSpot's file storage. We map each file to its parent record (contact, company, or deal). HubSpot's file size limits (25 MB per file) apply; files exceeding this limit are flagged for manual handling.

User.com custom object types map to HubSpot custom objects only on Enterprise plans. On Professional and lower tiers, each custom object becomes a set of custom properties on the nearest HubSpot standard object (Contact or Company). We document which objects were converted and flag relationship fields for junction-object creation.

User.com owner records are matched to HubSpot owners by email address. Unmatched owners are flagged before migration; your team either creates HubSpot user accounts for them or assigns records to a fallback owner. No record lands in HubSpot without a resolved owner.