Migrate from iPresso to Salesforce Sales Cloud

iPresso Contacts with Lifecycle Stage of subscriber, prospect, or unqualified lead map to Salesforce Lead. Contacts with Lifecycle Stage of MQL, SQL, customer, or evangelist map to Salesforce Contact tied to an Account. We compute the split at migration time using iPresso's lifecycle_stage and contact_status properties, and preserve the original stage in a custom field ipresso_lifecycle__c on both Lead and Contact for audit and reporting continuity. If iPresso stores behavioral scores or lead grades as custom properties, those map to custom fields on Lead (for unqualified) or Contact (for qualified).

iPresso Company records map directly to Salesforce Account. The iPresso company_name becomes Account Name, industry classification maps to Industry picklist, and any company-level custom fields map to custom Account fields. Account is created before Contact import so the AccountId lookup is satisfied at the moment of Contact insert. We use company domain as a secondary dedupe key if the customer uses domain-based Account matching in Salesforce.

iPresso Campaigns migrate to Salesforce Campaign records with Campaign Name, Type, Status, and Start/End dates preserved. The key difference is that iPresso stores behavioral audience rules and segment membership natively within the campaign; Salesforce Campaign does not replicate this logic. We migrate the list of contacts who were members of each campaign as Salesforce CampaignMember records with the appropriate Member Status (Sent, Responded, Opened). The behavioral segmentation logic itself is delivered as a written document for the customer's admin to rebuild using Salesforce List Views, Reports, or Flow-based segmentation.

iPresso contact tags migrate to Salesforce as either a custom multi-select picklist field on Contact (if tag count is under 150 and the customer prefers a single-field view) or as Salesforce Topics with TopicAssignment records (if tag count exceeds picklist limits or the customer prefers a flexible tagging model). The customer selects the strategy during scoping. We preserve the full tag membership list as a semicolon-delimited string in the target field during migration so no tag data is lost regardless of strategy.

iPresso multi-step automation sequences (workflows) do not migrate as code because Salesforce Flow is a different automation model with distinct trigger types, action libraries, and governor limits. We deliver a written workflow inventory that lists every active iPresso workflow with its trigger conditions, steps, time delays, channel assignments, and tag operations, plus a recommended Salesforce Flow type (record-triggered, scheduled, or screen) for each. The customer's Salesforce admin rebuilds the automations post-migration; a Salesforce implementation partner can be engaged for this scope if needed.

iPresso channel configurations (sender identities, SMS provider credentials, web push settings) require explicit reconfiguration in Salesforce. Email channel sender profiles and delivery settings map to Salesforce's standard Email Deliverability settings and any connected email app (Salesforce Inbox or a third-party email integration). SMS channel does not map directly; if the customer uses iPresso SMS, we document the SMS provider (API key, sender ID, opt-out handling) and recommend a Salesforce-compatible SMS app from the AppExchange (such as Twilio for Salesforce or SMS Magic) as the replacement. Web push and print channels have no Salesforce equivalent and are flagged for manual rebuild in the handoff document.

iPresso custom properties on Contacts and Companies map to Salesforce custom fields of equivalent type (text, number, date, picklist, checkbox, currency). We pre-create the Salesforce custom field schema in a Sandbox org before migration, including field-level security assignments and page layout additions. Picklist values from iPresso migrate to Salesforce picklist options; long-text custom properties migrate to Salesforce long-textarea fields. Validation rules on Salesforce custom fields may need to be relaxed during the migration load window to avoid rejecting records with legacy data that predates current picklist constraints.

iPresso email template HTML content migrates to Salesforce Email Templates (text or HTML). Dynamic personalization tokens referencing iPresso contact properties (such as {{contact.first_name}} or {{contact.company}}) require field reference updates to Salesforce merge field syntax (such as {!Contact.FirstName}). We deliver a token mapping table alongside the migrated templates so the customer's admin can update merge fields in bulk. Images and attachments embedded in iPresso templates migrate as Salesforce Static Resources or ContentDocument records with ContentDocumentLink associations.

iPresso drag-and-drop landing pages do not export as reusable templates. Page content, form field layouts, and thank-you page configurations cannot be directly migrated to Salesforce. We deliver a written inventory of every iPresso landing page with its URL, form field list, and submission target (campaign enrollment, tag assignment, workflow trigger). The customer's admin rebuilds these as Salesforce Experience Cloud Community pages, Web-to-Lead forms, or a third-party landing page tool (such as HubSpot, Unbounce, or WordPress) depending on the customer's preferred stack.

iPresso Enterprise tier includes vertical-specific solutions for FMCG, Finance, Education, e-commerce, and Travel with custom workflows, compliance fields, and reporting structures. These are iPresso-specific configurations with no direct Salesforce equivalent. We map each industry solution's data entities to Salesforce custom objects or standard objects (Case, Task, Custom Object) with custom fields matching the original data schema. Compliance requirements specific to Finance (such as regulatory audit fields) or Healthcare (HIPAA-related) require additional scoping and may need a Salesforce Shield or compliance add-on, which we flag during discovery.

iPresso stores campaign interaction history (opens, clicks, unsubscribes, form submissions) as behavioral event records tied to contacts. We migrate the most recent 12-24 months of interaction history as Salesforce CampaignMember records with appropriate Status values (Sent, Opened, Clicked, Unsubscribed, Converted). Older historical events are migrated as custom Activity records on the Contact or as a custom CampaignEvent__c object if the customer needs granular event-level history rather than summary status. The scope of interaction history to migrate is agreed upon during scoping because large event volumes affect Bulk API job sizing.

iPresso does not expose an explicit user/owner object via its API, but contact and company records reference an owner or agent field. We extract all distinct owner identifiers from the source data and match them by email against the Salesforce destination org's User table. Any owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Salesforce Users can be used for historical record assignment if the original iPresso owner is no longer active.