Migrate from eMarketeer to Pipedrive

eMarketeer Contacts map directly to Pipedrive People. Standard fields (email, first name, last name, phone, address) map to their Pipedrive equivalents. Lifecycle stage data from eMarketeer (subscriber, lead, customer, etc.) migrates to a custom Person field lifecycle_stage__c so that the customer's admin can use it for segmentation and reporting after cutover.

eMarketeer Contacts with an associated company name but no separate company object map to a Pipedrive Person with an Organization created on-the-fly during import. If the source eMarketeer account has a separate Companies object, we create Organization records first, then link Person records via the organization_id lookup.

eMarketeer Campaigns map partially to Pipedrive Deals where the campaign represents a sales opportunity with a value and stage. Campaign send history (subject, send date, recipient count, open rate, click rate) migrates as Notes attached to the Deal for audit purposes. Campaign performance metrics are not native Pipedrive objects; we preserve them as structured notes rather than as dashboard data.

eMarketeer Segments are defined by real-time criteria rules that re-evaluate continuously. Pipedrive does not support real-time dynamic segments — it uses static audience lists. We snapshot the current segment membership at cutover, create a Pipedrive static People list with the same name, and import all matching Person records into that list. The customer's admin should be aware that the Pipedrive list is a point-in-time snapshot and will not update automatically unless rebuilt with Pipedrive's filter logic.

eMarketeer Flows are automation sequences with trigger-action logic (contact enters segment, wait N days, send email, update property). Flow definitions do not migrate to Pipedrive because Pipedrive Workflow Automation uses a different trigger model and action set. We audit every active Flow during discovery, document its trigger type, step sequence, conditions, and delays in a written handoff document, and the customer's admin rebuilds equivalent automations in Pipedrive Workflow Automation post-migration.

eMarketeer Events with registration and attendance data map to Pipedrive Activities of type Meeting. Registration count, attendee list (linked by Person), and custom event type fields migrate to Activity custom fields. Check-in status and session-level attendance require field-level mapping depending on the source schema, which we derive from the export during discovery.

eMarketeer custom properties on Contacts (text, number, date, dropdown types) map to Pipedrive People custom fields. We derive the full custom property schema from the export because eMarketeer does not publish a field registry. Property enumerations (dropdown options) require explicit mapping to Pipedrive picklist values. Default values carry over unless the customer specifies otherwise during scoping.

Campaign-level custom properties migrate to Deal custom fields in Pipedrive. Where a campaign maps to a Deal, its custom properties attach to that Deal record. Properties with no corresponding Deal (campaigns stored purely as marketing records) migrate as Notes for manual reference.

eMarketeer email templates export as HTML blobs. Pipedrive does not store marketing email templates as a native object in the CRM core. We extract the HTML content and provide it to the customer as a structured file. Visual template editors with locked components may not reconstruct identically in Pipedrive Mailroom or any external email tool the customer adopts.

eMarketeer engagement events (open, click, unsubscribe per contact per campaign) aggregate into a contact activity log in Pipedrive. We migrate engagement timestamps as Activity records of type Email with a note describing the engagement type. Real-time engagement tracking (opens and clicks firing as events) requires the destination system's own email tracking to be active post-migration; the historical log provides a reference for past behavior but does not recreate live tracking.

SMS sends tracked as part of eMarketeer Flow execution migrate as Activity records with type Note describing the SMS content and send timestamp. Delivery receipts and opt-out states may require reconciliation against Pipedrive's HasOptedOutOfEmail field and any SMS integration the customer adopts post-migration (Pipedrive's SMS features are available through third-party integrations or the Sales Automation Advanced plan and above).

eMarketeer Owners (users who created or are assigned to records) map to Pipedrive Users by email match. We resolve all distinct owner references during discovery and flag any owner without a matching Pipedrive User for the customer's admin to provision before record import begins.