Migrate from Evam to Pipedrive

Evam Customer records map to Pipedrive People. Standard profile fields (name, email, phone, demographic attributes) map 1:1. Custom customer properties migrate as Pipedrive custom fields, with data type compatibility checked at scoping (text to text, number to number, date to date). Evam customer IDs are preserved in a custom field evam_customer_id__c as a migration audit trail and for any future reconciliation.

If Evam stores company-level groupings or organizational metadata on Customers, these map to Pipedrive Organizations. We extract the organization name from customer properties or related company records and create an Organization record before the Person import so that the Organization-Person link is satisfied at import time. Dedupe is performed on Organization name or domain.

Evam Deals (if present as a standalone object in the customer's data model) map to Pipedrive Deals. Deal name, value, stage, owner, expected close date, and custom deal properties migrate directly. Evam deal stages map to Pipedrive Deal stages, which we configure as a pipeline during the schema design phase. Pipedrive's visual pipeline stages and drag-and-drop interface are preserved as the primary deal tracking interface.

Evam behavioral events (page views, link clicks, purchases, custom events) do not have a native Pipedrive equivalent because Pipedrive is not an event-stream platform. We transform event history into Pipedrive Notes attached to the corresponding Person record. Each Note captures the event type, timestamp, and payload as structured text. We scope event exports to the last 90-180 days to stay within migration scope and API quota. Older events are documented as a representative sample for the customer's analytics team.

Evam customer segments (rule-based groupings for journey entry) map to Pipedrive Filters (saved filter views) and Labels (tag-style classification). We document the segment membership criteria during discovery and rebuild them as Pipedrive filter conditions on the Person object. Labels are applied as a flat classification layer for segments that operated on a tag basis. Complex segments with nested conditions that have no Pipedrive filter equivalent are flagged for manual rebuild or a separate segmentation tool.

Evam campaigns attached to journey steps map to Pipedrive Activities (tasks and events). Campaign metadata (name, status, dates, channel assignments) migrates as structured notes or custom fields. Campaign performance metrics (open rates, click rates, conversion rates) do not migrate because they are derived post-campaign and require the Evam analytics environment to reconstruct. We deliver a campaign inventory document listing every campaign with its metadata for the customer's team to recreate reporting in Pipedrive.

Evam channel configurations (SMS sender IDs, push notification credentials, in-app message templates) are environment-locked and cannot be moved to Pipedrive. We document the full channel configuration during discovery and deliver a re-setup checklist so the customer's operations team can re-register credentials in their chosen messaging platforms before cutover. Pipedrive Activities (calls, emails) serve as the activity record for the sales engagement layer, but channel messaging (SMS, push) requires a separate communications tool integration.

Evam extended properties on Customers migrate as Pipedrive custom fields on the Person object. We map data types explicitly: text properties to text fields, numeric properties to number fields, date properties to date fields, multi-select properties to multiple-choice fields. Picklist values migrate as Pipedrive option sets. Custom field naming is preserved with a migration prefix evam_ for audit traceability.

Evam Journey definitions (step sequences, branch conditions, wait timers, entry/exit rules) are not exportable from Evam's documented API. We perform a manual journey audit during discovery, documenting every active journey with its trigger conditions, step logic, and channel actions. This documentation is delivered as a written inventory for the customer's team to rebuild in Pipedrive Workflows (available from the Advanced plan) or a separate marketing automation platform. Journeys are not migrated as executable code.

Evam's AI-based predictive propensity scores are computed in Evam's runtime environment and are not accessible via the documented API. We cannot migrate these scores directly. Customers relying on AI-driven routing in journeys should plan to re-run scoring in Pipedrive's AI Sales Assistant (available on Advanced plan and above) or a third-party scoring layer post-migration. We document the score fields that existed in Evam so that the customer can re-establish scoring on the migrated contact records.