Migrate from iPresso to HubSpot

ipresso contacts map directly to HubSpot Contacts. Email, phone, and standard demographic properties map as-is. Custom contact properties that have no HubSpot equivalent are created as HubSpot custom properties before migration, and property type (text, number, date, picklist) is preserved during field creation.

ipresso's behavioral and engagement scoring is numeric but stored as a contact property. HubSpot has no native scoring field on Contact — the score migrates to a custom number property (e.g., ipresso_score__c) that your team can use in HubSpot workflows or list segmentation.

ipresso company records map to HubSpot Companies. Name, domain, industry, and employee count map directly. Parent-child company hierarchies in ipresso map to HubSpot's parent company association. Multi-company contacts (N:1 in ipresso) collapse to a primary company association in HubSpot with additional associations surfaced as secondary.

ipresso campaign membership (which contacts received which campaign communications) maps to HubSpot contact lists and contact properties indicating campaign membership. HubSpot's Lists model is the closest structural equivalent to ipresso campaign segments. Campaign-level engagement metrics (opens, clicks) are stored as engagement history rather than aggregated campaign stats.

ipresso has no native deal object — deal data stored as custom contact or company properties (e.g., deal_amount, deal_stage, close_date) must be extracted and reshaped into HubSpot Deals. Each unique deal identifier in ipresso becomes a HubSpot Deal record. The deal's associated contact or company links via HubSpot's deal associations.

ipresso stage values stored in custom fields map to HubSpot deal pipeline stages. We read the source stage values and create corresponding HubSpot pipeline stages during pre-migration setup. Probability values associated with stages in ipresso are preserved as HubSpot stage probabilities on the Deal object.

ipresso email engagement events (sent, delivered, opened, clicked, bounced) map to HubSpot engagement timeline entries on the Contact record. Each engagement event creates a distinct activity with original timestamp and channel type preserved. The engagement type is set to 'EMAIL' for all email-related events.

ipresso SMS events (sent, delivered, clicked) map to HubSpot engagement timeline entries with type 'SMS'. HubSpot's native SMS tracking requires a connected SMS provider (Twilio, or a HubSpot native SMS add-on); we log the engagement events regardless and flag that live SMS tracking requires post-migration configuration.

ipresso's web push and banner notification events have no direct HubSpot equivalent. Engagement records are logged as custom activities on the Contact with the channel type stored as a property (e.g., push_notification_sent). Campaign association is preserved via the activity's associated campaign identifier.

ipresso user records map to HubSpot Users by email match. Unmatched ipresso owners are flagged before migration — your team either creates HubSpot user accounts for them or assigns their records to a designated fallback owner. No contact lands without a HubSpot owner assignment.

Any ipresso custom contact property that does not match a HubSpot native property name or type is created as a HubSpot custom property before migration. Property types (single-line text, multi-line text, number, date, checkbox, select) are mapped to HubSpot equivalents. Select (picklist) properties require value-by-value mapping if ipresso uses closed picklists.

ipresso files attached to contacts or companies are downloaded and re-uploaded to HubSpot Files. File size limits apply (HubSpot default 25MB per file; larger files split or linked). File associations to contacts or companies are recreated using HubSpot's file attachment feature on the relevant record.