Migrate from e-shot to Pipedrive

e-shot Contacts map to Pipedrive People. The contact email address is the dedupe key used to detect existing records during import. All standard system fields (email, first name, last name, phone, address) map to Pipedrive Person fields. We extract the full custom contact field schema from Settings > Contacts field manager, pre-create equivalent Pipedrive custom fields before contact load, and map each field value by name. Merge-tag fallback definitions become Pipedrive default field values pre-set before any contacts are inserted so that contacts missing source values display cleanly rather than showing raw merge-tag syntax.

e-shot's contact field schema is fully customisable per account. We export the field name, type (text, number, date, checkbox, dropdown), and merge-tag fallback definitions during scoping. Each field maps to a Pipedrive Person custom field of equivalent type. The customer provisions these custom fields in Pipedrive Settings > Custom Fields before the migration contact load phase begins. Field ordering and grouping in Pipedrive's detail view are documented separately for the admin to configure.

e-shot campaign records map to Pipedrive Deals, using the campaign name as the Deal title and the campaign creation date as the Deal open date. Campaign status (live, draft, archived) maps to a custom Deal field rather than a native Pipedrive status. Note that campaign email content, subject lines, sender details, and HTML body do not migrate — Pipedrive is a CRM and has no native email campaign storage. We create a deal per campaign so that the customer's sales team can link People and Organizations to campaign-sourced leads.

e-shot Automated Series are email sequences triggered by behaviour or date conditions. These split into two Pipedrive artefacts: the series itself becomes a linked Deal (representing the campaign arc) and individual step timestamps migrate as Task records with due dates and notes describing each step. The series trigger condition (tag applied, date reached, form submitted) is stored as a custom Deal field for the admin to reference when rebuilding the logic in a marketing automation tool. This split preserves the historical sequence timeline but does not reproduce active automation — rebuild is required.

e-shot Forms capture contact inputs and subscription preferences. Form field definitions map to Pipedrive Person custom fields. Form submission events (timestamp, source form, field values) migrate as Person records with custom field values populated from the submission data. If a form collects data for multiple contacts (e.g. event registration), each submitted entry becomes a separate Person record.

Contact-level opt-in status and subscription interests stored as active Preferences in e-shot map to Pipedrive Person custom fields (e.g. email_consent, sms_consent, product_interests). Tier limits apply to active Preferences (basic: 25, pro: 50, omni: unlimited) — we query the active flag during scoping to migrate only live preferences. Where a preference change has a timestamp (subscription updated date), we record it as a Person Activity Note in Pipedrive.

e-shot supports company-level fields on contacts (company name, website, industry). If the customer has used e-shot's company attributes on contacts, we extract distinct company values and map them to Pipedrive Organizations, then resolve the Organization ID on each Person record during contact load. Company name becomes the Organization name, website maps to Organization website field.

e-shot tags label contacts and segments but are stored as field values or list memberships rather than a dedicated tag object. We extract all distinct tag values, create matching Pipedrive Labels, and attach label assignments to the corresponding Person records. Tags used for segmentation logic (dynamic filter-based segments) are noted in the deliverable for the admin to replicate using Pipedrive's filter and list views.

Historical campaign analytics (opens, clicks, bounces, unsubscribes, delivery rate) exportable from e-shot's analytics dashboard migrate as custom fields on the corresponding Deal record plus an Activity Note summarising the campaign performance snapshot. These are historical reference values, not live reporting. Pipedrive's native reporting covers pipeline and sales activity but not email engagement metrics.

e-shot saved filters define dynamic contact segments using field conditions. We export the filter definition (field names, operators, values) in the handoff document. Pipedrive's filter and list view functionality is equivalent but not identical in operator syntax. The customer rebuilds each saved filter as a Pipedrive filter during the post-migration review period.