Migrate from OnePageCRM to Pipedrive

OnePageCRM Contact records map directly to Pipedrive Person. We carry name, emails, phones, addresses, social URLs, and all custom contact fields. The dedupe key is email address (lowercased, stripped of formatting). Pre-migration deduplication removes exact email duplicates before insert. Any Person record without an email address is imported with a placeholder flag for the customer's admin to resolve post-migration.

OnePageCRM Organization records map to Pipedrive Organization. We carry company name, phone, address, website, and custom company fields. Organization is imported before Person records so that the Person-Organization link (stored as org_id on OnePageCRM Contact) is satisfied at insert time. If a Contact has no linked Organization, we leave the org_id field null and document it for manual linking.

OnePageCRM Deals map to Pipedrive Deals with deal name, amount, expected close date, margin, commission, and cost fields carried directly. The OnePageCRM pipeline and stage assignment maps to a Pipedrive Pipeline with matching stage values. We create the Pipedrive pipeline and stages during the schema setup phase before any Deal records are loaded. Closed-Won and Closed-Lost status from OnePageCRM migrate as Pipedrive Stage names with the relevant probability percentage.

OnePageCRM Status taxonomy (typically: New, Prospect, Qualified, Proposal Sent, Customer, Inactive) maps to Pipedrive pipeline stages. We create a single Pipedrive pipeline during setup and configure one stage per OnePageCRM Status value, preserving the ordering. If OnePageCRM has multiple custom statuses, we create matching stages and flag any that have no natural Pipedrive equivalent (e.g., if 'On Hold' is a status rather than a deal stage, it may become a Deal label or custom field instead).

OnePageCRM Next Action (the date and text of the next required follow-up) decomposes into a Pipedrive Activity with type=task, due_date=Next Action date, and subject=Next Action text. We replay Next Actions as open, uncompleted tasks on the linked Person. Any Next Action with a past due date is imported as an overdue task flagged in the migration report. Completed Next Actions are imported as completed activities with the completion timestamp preserved.

OnePageCRM tags assigned to Contacts map to Pipedrive Person Labels. If tags are also assigned to Deals in OnePageCRM, those map to Pipedrive Deal Labels. We preserve the flat tag namespace without flattening or hierarchy since OnePageCRM does not use tag parent-child structures. Labels with identical names across Person and Deal namespaces are created separately in each context and are not shared.

OnePageCRM Lead Source (how the contact entered the CRM, e.g., Website, Referral, Trade Show) is a contact-level property. We map this to a Pipedrive custom field on Person named Lead Source. If the customer uses Lead Source at the deal level, we add an equivalent custom field on Deal. We create the picklist values in Pipedrive matching the OnePageCRM source list exactly during the schema setup phase.

OnePageCRM notes and call logs attached to Contacts export as structured records in the Contacts export dataset. We replay notes as Pipedrive Person Activities with type=note and the note body in the content field. Call logs replay as Pipedrive Activities with type=call, call_duration (from duration field if present), and call outcome mapped to a custom call outcome field. Note and call timestamps are preserved as the Activity start time.

OnePageCRM Predefined Actions are saved task sequences assigned to contacts (e.g., 'Follow up after demo', 'Send proposal week 1'). We do not migrate these as Pipedrive workflow automations because the two systems use different automation models. Instead, we deliver a written inventory of every unique Predefined Action template with its action steps, assigned labels, and a recommended Pipedrive Task Template equivalent. The customer's admin creates the Pipedrive Task Templates and assigns them manually post-migration.

OnePageCRM Predefined Items (products or services used in deal creation) map to Pipedrive Products. We carry item name, price, unit, and grouping. If OnePageCRM uses item grouping (e.g., by product line), we map this to Pipedrive Product category. Product associations to Deals (line items) are resolved by matching on deal_id and item_id during the Deal import phase.

OnePageCRM custom contact fields must be pre-created in Pipedrive before Person import. We audit the source custom field schema during scoping, generate the Pipedrive custom field creation checklist, and the customer creates these fields in Pipedrive Settings before migration day. Field types are mapped: text to string, number to number, date to date, dropdown to picklist. Any OnePageCRM field type with no Pipedrive equivalent (e.g., multi-select text) becomes a string field with delimiter-separated values.

Deal-level custom fields from OnePageCRM (margin percentage, commission rate, cost fields) map to Pipedrive deal custom fields. We apply the same pre-creation requirement and type mapping as Person-level fields. Character limits in Pipedrive custom fields are checked against source data length; any field with values exceeding Pipedrive limits is flagged and truncated with a note in the migration report.