Migrate from eZnet CRM to Pipedrive

eZnet CRM Accounts map directly to Pipedrive Organizations. The Account name, website, address fields, phone, and industry classification migrate to the corresponding Organization fields. Account is imported before any Person or Deal to satisfy Pipedrive's foreign-key relationships. We use Organization name as the deduplication key and flag any eZnet Accounts with duplicate names for the customer's admin to resolve before final import.

eZnet CRM Contacts map to Pipedrive People. Each Person is linked to a parent Organization (resolved by matching the eZnet Account name or domain). Name, email, phone, title, and address fields migrate directly. eZnet's Account-Contact associations are preserved by resolving the target Organization UUID at import time and setting the Person's organization_id.

eZnet CRM Leads (distinct from Opportunities) map to Pipedrive Leads. Lead status, source, and any custom lead fields migrate to Pipedrive's Lead object fields. Pipedrive's Lead object is separate from Person and can be converted to a Person-Organization combination during or after migration, which we document as a post-migration workflow step.

eZnet CRM Opportunities map to Pipedrive Deals. Stage name from eZnet maps to the target Pipedrive pipeline stage; we configure the Pipedrive pipeline stages before migration to match eZnet's stage names and order. Expected close date, deal value, and probability migrate to Pipedrive's close_date, value, and probability fields. Each Deal is linked to the parent Organization (and optionally Person) by resolving the eZnet Account and Contact references.

eZnet CRM pipeline and stage configuration (stage names, order, win/loss definitions) is captured during discovery and mapped to Pipedrive Pipeline objects. We create Pipedrive Pipelines with matching stage names and sequence before Deal import. Probability percentages per stage migrate to Pipedrive's stage-level probability settings.

eZnet CRM Activities (calls, emails, tasks, meetings) map to Pipedrive Activities with the corresponding type field (call, email, task, meeting). Activity date, duration (for calls), notes, and subject migrate directly. We resolve the parent Person or Organization reference by matching eZnet Contact and Account names against the imported Pipedrive records. The activity type field determines which Pipedrive activity endpoint is used during import.

eZnet CRM Document Library metadata (file name, description, linked Account or Contact) migrates as Pipedrive Notes or attachments linked to the parent Organization or Person. Actual file blobs require separate handling and are flagged during scoping; we provide a written checklist for file migration including target path structure in Pipedrive's file storage model.

eZnet CRM custom fields (Standard tier and above) are captured with their data type, picklist values, and visibility settings during discovery. We pre-create the equivalent Pipedrive custom fields (using Pipedrive's field type system: text, numeric, date, dropdown, checkbox, etc.) before any record import so that the mapping is in place at insert time. Picklist values migrate as Pipedrive drop-down options.

eZnet CRM Users and role-based assignments export as Pipedrive Users. We match by email address. Any eZnet User without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive eZnet users are preserved as historical Deal and Activity owners where the original owner context is needed.

eZnet CRM Marketing Campaign records and associated email marketing data migrate to Pipedrive Campaigns. Campaign member associations to Contacts are preserved where possible; Pipedrive's campaign membership model differs from eZnet's, so we document the mapping and flag any associations that require manual reassignment in Pipedrive's campaign interface post-migration.

eZnet CRM Inventory Items (Professional tier and above) export with item records, stock levels, and pricing. These map to Pipedrive Products. Unit price, SKU, and description migrate to Pipedrive's corresponding Product fields. Products can be linked to Deals via the Deal-Product association if the customer uses Pipedrive's product-linking feature.

eZnet CRM email integration metadata (which Contact and Account an email is associated with) migrates to Pipedrive Activities of type email. The email subject, body, timestamp, and sender/recipient information are mapped to Pipedrive's activity fields. Full email threading and attachment content require separate handling based on what eZnet's export mechanism exposes.