Migrate from crmConnect to Pipedrive

crmConnect Contact records map directly to Pipedrive People. Standard fields (name, email, phone, address) transfer 1:1. crmConnect's duplicate guest card issue means we run a dedup pass on name and email before import, merging records with identical email addresses. Custom contact properties discovered during export map to Pipedrive custom fields on People. We preserve crmConnect tag associations as person notes or as a comma-separated custom field for admin reference.

crmConnect Company records map to Pipedrive Organization. If crmConnect is used primarily as a contact-only CRM, we skip Organization creation and link People directly to Deals. If Company records exist, we use the domain field as the Organization website and as the dedupe key. crmConnect's Company-phone-email structure maps to Organization phone, primary email, and address fields.

crmConnect Pipeline maps to Pipedrive Pipeline. crmConnect Standard supports 1 pipeline with 5 opportunities; Professional supports the same single pipeline but with unlimited opportunities. Pipedrive supports unlimited pipelines from any tier. We migrate stage names, stage order, and probability percentages as Pipeline stage configuration. Stage names longer than 50 characters are truncated to Pipedrive's limit. We flag if the customer requires multiple Pipedrive pipelines for multi-line-of-business segmentation and configure those before migration.

crmConnect Opportunities map to Pipedrive Deals. Deal title, amount, currency, stage assignment, expected close date, and owner (resolved by email match to Pipedrive User) transfer directly. Custom opportunity fields map to Pipedrive custom fields on Deal. If crmConnect Opportunity has a linked Contact, we resolve the Person record before inserting the Deal so the Person-Deal link is established at migration time. Lost-won reason custom properties map to Pipedrive's Lost reason field or a custom field for deal history.

crmConnect Calendar events map to Pipedrive Activity records with type Event. Event title, start time, end time, location, and attendee list (linked Contact names) transfer. crmConnect Standard limits to 1 calendar; Professional supports unlimited. We flag calendar records tied to inactive or departed users for admin review before migration. Recurring event patterns in crmConnect are captured as a text note on the first Event record since Pipedrive Activities do not support recurrence natively.

crmConnect automations (drag-and-drop workflow builder) do not migrate to Pipedrive because the automation models are structurally different. crmConnect Professional offers unlimited automations with triggers, conditions, and actions that have no direct Pipedrive equivalent. We capture automation intent: trigger events, condition branches, action types, and delay steps are documented in a written inventory delivered to the customer. Pipedrive's workflow automations (available on Advanced and above) are rebuilt by the customer's admin using the inventory as a guide. This is not a data migration; it is a discovery and documentation scope.

crmConnect memberships and course enrollments are separate record types on Professional tier with enrollment status, start date, course name, and completion date. Pipedrive does not have a custom objects feature, so we map these to custom fields on the Person record: membership_status__c (picklist), enrollment_date__c (date), course_name__c (text), and completion_date__c (date). If a contact has multiple course enrollments, we store them as newline-delimited text in course_history__c. The customer should confirm whether membership and course data is business-critical before including it in scope.

crmConnect Professional supports up to 6 products in the built-in e-commerce store. Product name, price, and association to contacts (as order records) map to Pipedrive Products. Pipedrive Products link to Deals via the product_id field on Deal line items. If the customer uses crmConnect's order and payment history, we map those as Activity records with type Note or as custom fields on the related Deal, depending on the record volume. crmConnect text-to-pay and invoice records are out of scope.

crmConnect email campaign templates and send history export as text and metadata. We export template structure (subject, body HTML, link URLs) as a structured document. Pipedrive does not have a native email blast tool on all tiers; email sequences require Growth plan ($49/user/month). We do not migrate email campaigns as functional templates. The template export document is handed to the customer's admin or email marketing partner to rebuild in Pipedrive, Mailchimp, or another dedicated email platform.

crmConnect Professional supports 3 SMS text blast sequences with subscriber lists. SMS sequences are a marketing engagement feature with no direct Pipedrive equivalent at the Essentials-Advanced tiers; Growth plan includes Sequences but they are sales cadence tools rather than bulk SMS blast tools. We export sequence definitions and subscriber lists as structured CSV. The customer decides whether SMS moves to a dedicated SMS platform (Twilio, Attio, or similar) or is rebuilt in Pipedrive Sequences if the Growth plan is selected.

crmConnect funnels and landing pages are content objects rather than CRM data records. We export funnel structure and page content as a template document with screenshots. Pipedrive is a sales CRM and does not include a funnel or landing page builder. These assets require rebuild in a dedicated landing page tool (Carrd, Unbounce, WordPress) or a marketing platform. We do not migrate funnel or page code. The content export supports the customer's web team in recreating the structure.

crmConnect contact tags and list segments export as tag-to-contact mappings. We restore tag associations as a comma-separated text custom field on the Person record (e.g., vip__c, enterprise__c, webinar-q1-2025). Pipedrive Organization-level tags are available on Advanced and above and can be used if the tag applies to a company rather than a person. Segment membership (static lists) exports as a notes field noting the segment name. The customer chooses whether to use custom fields or manual list management in Pipedrive.