Migrate from iPresso to Pipedrive

iPresso Contact records map directly to Pipedrive Person. Core profile fields (name, email, phone, address) migrate via direct field mapping. The iPresso lifecycle stage property maps to a custom Person field lifecycle_stage__c that we create in Pipedrive during schema setup. Behavioral event data (page views, email opens, campaign interactions) exceeds Pipedrive's native activity model; we store the most recent event summary as a custom field and full interaction history as linked activity notes.

iPresso Company records map to Pipedrive Organization. Company-level custom fields, industry classifications, and address data migrate directly. Organization is created before Person import so that the organization_id lookup is resolved at the moment of Person insert, preventing orphaned contact records without a parent organization.

iPresso Deal records map to Pipedrive Deal. The iPresso deal stage and pipeline assignments map to Pipedrive Pipeline stage values that we configure before migration. Deal value, expected close date, owner assignment, and custom deal fields migrate directly. If iPresso uses multiple deal pipelines, each maps to a separate Pipedrive Pipeline object with its own stage configuration.

Pipedrive has no native campaign object. iPresso campaign records (channel type, audience segment, send date, open/click/send counts) are reconstructed as Pipedrive Activity Notes linked to the relevant Person or Organization. We create a custom field campaign_channel__c on Person to store the most recent channel type and a custom field campaign_name__c for campaign attribution. Campaign analytics (open rates, click rates) are stored as custom numeric fields on the linked Person record rather than as aggregate campaign metrics.

iPresso contact segmentation tags migrate to Pipedrive Labels. Tag memberships are one-to-one: a contact with tags A, B, C in iPresso receives Labels A, B, C on the equivalent Person record in Pipedrive. Labels in Pipedrive are per-object (Person Labels, Organization Labels, Deal Labels), so tag scope decisions (which object the tag applies to) are made during scoping based on how the customer used tags in iPresso.

iPresso email template HTML content migrates to Pipedrive Email Templates. Dynamic personalization tokens referencing iPresso contact properties (e.g., first name, company name, custom fields) require field reference updates to Pipedrive's template token format. Static templates without dynamic tokens migrate without transformation. Templates using iPresso-specific merge field syntax are flagged and delivered with a reconfiguration note for the customer's admin.

iPresso email engagement records (send events, opens, clicks) map to Pipedrive Activity records of type email linked to the relevant Person. The activity subject carries the campaign or send reference, the body carries email content, and timestamp preserves send or open date. We resolve the Person lookup by email address at migration time.

iPresso call engagement records map to Pipedrive Activity records with type set to call. Call duration, disposition, and recording URL transfer to custom activity fields. Activity timestamp preserves the original call date. Owner assignment resolves by matching iPresso owner email to Pipedrive user email.

iPresso meeting engagement records map to Pipedrive Activity records with type set to meeting. Start and end time, location, and attendee list migrate directly. Attendee email addresses resolve to Pipedrive Person records via email match where applicable.

iPresso note engagements map to Pipedrive Activity Note records. Rich text content, attachment references, and timestamp migrate directly. Note is linked to the parent Person or Organization record. Attachment files are stored separately and reattached to the Pipedrive Activity Note via the Files API.

iPresso contact custom fields map to Pipedrive Person custom fields of the equivalent type. Text fields map to text, date fields to date, numeric fields to number, and picklist fields to picklist. We create all destination custom fields in Pipedrive before importing data so that the import process can write directly to typed fields without post-migration type conversion. Picklist values migrate as-is; the customer should review value spelling and remove duplicates during scoping.

iPresso company custom fields map to Pipedrive Organization custom fields. Same type-mapped approach as contact custom fields. Organization-level custom fields that reference hierarchical structures (e.g., parent company, subsidiary relationships) are flattened into text fields in Pipedrive unless the customer elects to use Pipedrive's custom entity model for subsidiary tracking.

iPresso owner records referenced on Contacts, Companies, and Deals are resolved by email match against Pipedrive User accounts. Owners without a matching Pipedrive User go to a reconciliation queue before migration of record-dependent objects begins. The customer's Pipedrive admin provisions missing users (or marks them inactive if the original owner is no longer active in iPresso). Migration cannot proceed past owner reconciliation because OwnerId references are required on standard Pipedrive objects.

iPresso Workflows are multi-step automation sequences with channel triggers, conditions, and time delays. They do not migrate as executable code to Pipedrive because Pipedrive Automation Rules use a different trigger-action model. We extract every active iPresso Workflow with its trigger conditions, step sequence, channel assignments, and delay logic, and deliver this as a written inventory document. The customer's Pipedrive admin rebuilds equivalents using Pipedrive Automation Rules (Professional and above) or a third-party integration tool such as Zapier or Make.