Migrate from SuiteCRM to Pipedrive

SuiteCRM Accounts map directly to Pipedrive Organizations. The Account name becomes Organization name, website becomes the URL field, industry maps to a Pipedrive custom field if the customer tracks industry on Organization. We extract Account records first so that the Organization ID is available as a lookup when Contact import begins. SuiteCRM subpanel data (child Contacts, Opportunities) is resolved via the relationship tables during the Contact mapping phase.

SuiteCRM Contacts map to Pipedrive Persons with the primary Account link resolved to the Organization ID. Name fields (first_name, last_name) map to Pipedrive Person name fields. Email, phone, title, department, and address fields migrate directly. SuiteCRM's primary_address and alt_address blocks map to Pipedrive's single address structure; if the customer uses both addresses, the secondary address migrates as a custom field.

SuiteCRM Leads map to Pipedrive Leads. Lead status, source, and rating fields migrate to Pipedrive custom Lead fields. The customer's SuiteCRM lead_status values are preserved as custom picklist values in Pipedrive. If the destination Pipedrive plan does not include Leads, Leads migrate as Persons with a custom lifecycle-stage field and a separate Pipeline for follow-up tracking.

SuiteCRM Opportunities map to Pipedrive Deals. Opportunity name, amount, close_date, sales_stage, probability, and Account link migrate to Deal title, value, close date, stage, and Organization link. We create the Pipedrive Pipeline and Stages before Deal import so that stage values match the SuiteCRM sales_stage enumeration. Closed-won and closed-lost reasons from SuiteCRM become custom Deal fields in Pipedrive.

SuiteCRM Products map to Pipedrive Products. The product catalogue (name, SKU, pricing, description, taxonomy) migrates to Pipedrive. We pre-create Products before any Deal import because Pipedrive requires Product IDs when adding line items to Deals. If the customer uses bundle products or product families in SuiteCRM, we map these to Pipedrive product categories.

SuiteCRM Cases (tracked in the Bugs module) have no native Pipedrive equivalent. During scoping we determine whether Cases should migrate as Deals in a dedicated support pipeline, as Activities attached to the relevant Person or Organization, or as a custom object. Most teams choose a Deal-based approach where each Case becomes a Deal with a custom case_number field and a status workflow built in Pipedrive Automation.

SuiteCRM Documents store files on the server filesystem (typically /upload/) with metadata in the database. We copy the physical files and upload them to Pipedrive as Files attached to the parent Organization, Person, or Deal record. This step requires the customer to provide server access or a database-plus-filesystem export. We validate file integrity checksums after extraction and verify each file is linked to the correct parent record after upload.

SuiteCRM engagements (calls logged via the Calls module, meetings via Meetings, tasks via Tasks, and emails via the EmailClient or archived emails) map to Pipedrive Activities. Each engagement type maps to the corresponding Pipedrive Activity type. We preserve the original timestamp, duration for calls, attendee list for meetings, and the activity body for notes. Activity records are linked to the parent Person or Deal by resolving the SuiteCRM relationship IDs at migration time.

SuiteCRM Contracts track agreement terms, start and end dates, and renewal status. Pipedrive has no native Contract object. We migrate contract records as custom fields on the parent Organization (contract start date, end date, renewal date, contract value) or as a linked Deal with custom fields capturing the same data. The customer chooses the strategy during scoping.

SuiteCRM Studio allows administrators to add custom fields to any module. These fields exist in extended database tables with a naming convention appended to the module name (e.g., accounts_cstm). We scan the database schema during discovery, extract every custom field with its data type, and pre-create matching custom fields in Pipedrive before data import. Dropdown and multiselect fields in SuiteCRM require the value list to be recreated as Pipedrive custom field options.

SuiteCRM Campaigns store campaign metadata (name, type, status, budget, start and end dates) and email response tracking. Pipedrive has no native Campaign object. We migrate campaign records as custom fields on the relevant Person records (campaign membership) or as a note on the linked Account. Campaign response data (opens, clicks) migrates as Activity log entries on the contacted Persons.

SuiteCRM Users map to Pipedrive Users by email match. We extract the Users table including username, email, and is_admin flag. On import, each SuiteCRM User is matched to the corresponding Pipedrive User record by email. Owners on Contacts, Accounts, Opportunities, and Activities are updated by resolving the User email to the Pipedrive user ID at migration time.