Migrate from iPresso to HighLevel

iPresso Contact records map to GoHighLevel Contact. The iPresso lifecycle stage property maps to a GoHighLevel custom field (contact_lifecycle_stage__c) since GoHighLevel does not have a native lifecycle stage property. Tag memberships on the contact are extracted as comma-separated values and written to a multi-select custom field or split into multiple single-value contact properties. Email address is the dedupe key; contacts without email are flagged for manual review during reconciliation.

iPresso Company records map to GoHighLevel Company. The iPresso company name becomes the Company Name field, domain becomes Website, and industry classification maps to a custom field or the built-in industry picklist. Company-level custom fields require field-level mapping to GoHighLevel Company custom fields, which must be created before import. Companies are imported before Contacts so that the parent reference can be resolved at Contact insert time.

iPresso Campaigns with active audience segments and deal values map to GoHighLevel Opportunities assigned to a Pipeline. The iPresso campaign status (active, paused, completed) informs the GoHighLevel Opportunity stage. Campaign interaction metrics (opens, clicks, sends) do not have a native GoHighLevel equivalent and are preserved as custom fields or recorded in a separate reporting document for the customer's admin to reference in dashboards.

iPresso audience segments tied to a campaign map to GoHighLevel Pipeline stages or Tags. We create a GoHighLevel Pipeline with stages representing each audience segment, and assign contacts to the appropriate stage based on their segment membership. Tags are applied for cross-segment segmentation that cannot be represented as a single pipeline stage.

iPresso tags are flat label memberships on contacts. We extract the full tag list and determine the migration strategy during scoping: for fewer than 50 tags, we create a GoHighLevel multi-select custom field (contact_tags__c) with all values as picklist options. For more than 50 tags or when tags represent behavioral data (e.g., campaign names), we map each tag to a GoHighLevel Tag and create TagAssignment records. The customer chooses the strategy before migration begins.

iPresso custom properties on contacts and companies are mapped to GoHighLevel custom fields of equivalent type: text to text, number to number, date to date, and picklist to picklist. We pre-create all GoHighLevel custom fields before import. Validation rules and conditional required fields in GoHighLevel must be identified and either temporarily disabled during import or accommodated in the data transform to prevent record rejection.

iPresso email templates with static HTML content migrate to GoHighLevel Email Templates directly. Dynamic personalization tokens referencing iPresso contact properties require field reference updates in GoHighLevel using the {{contact.field_name}} merge field syntax. Template subject lines and preheader text migrate as stored text. We flag any template that uses iPresso-specific merge field syntax for manual review before import.

iPresso engagement records (email sends, SMS messages, call logs, meeting records, notes) migrate to GoHighLevel Activity records. Email activities land as GoHighLevel Email records linked to the contact timeline; SMS logs land as SMS records; call dispositions and durations land as Task records with the Call subtype; meeting records land as Event records. Timestamps are preserved to maintain the activity timeline order. Engagement metadata (open tracking, click tracking) migrates as custom activity fields.

iPresso channel configurations (sender settings, SMS provider credentials, web push domain configuration) require manual reconfiguration in GoHighLevel. We document the current channel settings from iPresso during scoping and provide a configuration checklist for the customer's admin to implement in GoHighLevel. SMS sender IDs and phone numbers must be re-registered in GoHighLevel's integrated Twilio or LC Email setup. This is a manual rebuild step, not a data migration.