Migrate from iPresso to Microsoft Dynamics 365 Sales

iPresso Contacts with lifecycle stage values indicating prospect status (Subscriber, Lead, Marketing Qualified) map to Salesforce Lead. Contacts with lifecycle stage values indicating sales engagement (Sales Qualified, Customer, Evangelist) map to Salesforce Contact attached to an Account. We compute the split during the transform phase using iPresso's lifecycle_stage property, preserve the original value in a custom field ipresso_lifecycle__c on both Lead and Contact, and use email address as the dedupe key. Contact ownership (hubspot_owner_id equivalent) maps to Salesforce OwnerId via the User lookup.

iPresso Company records map directly to Salesforce Account. Company domain name from iPresso becomes the Account Website field and serves as the dedupe key. Industry classifications, annual revenue, employee count, and custom company fields migrate to typed Salesforce fields. Account is created before Contact import so that the AccountId lookup is satisfied at the moment of Contact insert to avoid orphaned records.

iPresso Campaign records map to Salesforce Campaign. Campaign name, type, status, start and end dates, budgeted cost, and actual cost transfer directly. Audience segments from iPresso (contact lists and tag-based filters) are recreated as Salesforce Campaign MemberStatuses. Note that iPresso's multi-channel campaign tracking (SMS, Push, Print sends and responses) has no direct Salesforce Campaign equivalent; we document the channel breakdown per campaign so the customer can assess whether Dynamics 365 Marketing module is needed.

iPresso contact segmentation tags migrate to Salesforce custom multi-select picklist fields on Contact and Lead. Tag names are preserved as picklist values. If tags are used for content or campaign classification rather than lead segmentation, we map them to Salesforce Topics with TopicAssignment records. The customer selects the tag strategy during scoping.

iPresso custom properties on Contacts and Companies require pre-creation in Salesforce before migration. We map iPresso field types (text, number, date, checkbox, dropdown) to Salesforce field types (Text, Number, Date, Checkbox, Picklist). Validation rules, required field constraints, and conditional display logic from iPresso are documented in the schema deliverable for the customer's admin to re-implement in Salesforce field settings.

iPresso email engagement records migrate to Salesforce EmailMessage (the email body and headers) linked to an Activity Task (the timeline entry). The WhoId on Task points to the migrated Lead or Contact; the WhatId points to the related Account or Opportunity if applicable. Email open and click event data from iPresso is preserved as custom Task fields since Salesforce Activity does not natively store marketing engagement metrics.

iPresso call engagements map to Salesforce Task with TaskSubtype = Call. Call disposition, duration in seconds, and any recording URL migrate to custom Task fields. ActivityDate is set to the original iPresso timestamp to preserve timeline ordering. Owner assignment migrates via Owner email lookup against the Salesforce User table.

iPresso meeting engagements map to Salesforce Event. StartDateTime, EndDateTime, Subject, Location, and Description transfer directly. Attendee information from iPresso creates EventRelation records pointing at the migrated Lead or Contact. Meeting outcome and status from iPresso become custom Event fields.

iPresso note engagements migrate to Salesforce Note records linked via ContentDocumentLink to the parent record (Lead, Contact, Account, or Opportunity). Note body migrates as rich text. Attachments migrate as ContentDocument records with ContentDocumentLink associations. Note timestamps are preserved in Salesforce to maintain the activity timeline.

iPresso multi-step automation sequences do not migrate as code to Microsoft Dynamics 365 Sales because the automation models differ structurally. We deliver a written Workflow Inventory documenting every active iPresso workflow with its trigger conditions, action sequence, time delays, and a recommended Power Automate or Dynamics 365 workflow equivalent. The customer's admin rebuilds workflows post-migration based on this inventory.