Migrate from Ploomes CRM to Pipedrive

Ploomes Contacts migrate to Pipedrive People. We preserve all standard contact fields (name, email, phone, address) plus CNPJ/CPF identification data as custom fields on the Person record. Brazilian CNPJ numbers map to a CNPJ custom field; CPF numbers map to a CPF custom field with the appropriate validation format. OrganizationId is set by resolving the Ploomes Company reference to the corresponding Pipedrive Organization ID after the Organization migration phase completes.

Ploomes Company records map to Pipedrive Organizations. Company name becomes Organization name, domain becomes Website, and any Brazilian state registration or CNPJ data migrates as custom fields on the Organization. Organization is created before Contact import to satisfy the OrganizationId lookup required on People records. Company-Custom Field associations preserve during migration.

Ploomes Deals migrate to Pipedrive Deals with deal title, value, stage, owner, and custom properties preserved. Pipeline stages from Ploomes are rebuilt as Pipedrive pipeline stages during the pre-migration configuration phase. Deal owner is resolved by matching the Ploomes owner email to the Pipedrive user email. API pagination at 300 records per request requires chunked extraction; we detect total deal count during discovery and loop through page offsets until all records are retrieved.

Ploomes pipeline stages are rebuilt in Pipedrive as named stages within the configured pipeline. Stage order and probability percentages migrate as configuration. We create the Pipedrive pipeline and stage structure before Deal import begins so that stage values are available for assignment during migration.

Ploomes Products with hierarchy (Groups and Parts) map to Pipedrive Products. Product name, SKU, unit price, and currency migrate. Pipedrive Products are activated for use in Deals during migration so that line items can reference them. Product-custom field associations preserve via the migrated custom field definitions.

Ploomes Quotes do not have a direct Pipedrive equivalent. Pipedrive has no native Quote object (Sales Docs is a paid add-on for document generation). We migrate Quote data as follows: Quote header fields (client name, date, total value) become custom fields on the linked Pipedrive Deal; Quote line items become Product entries linked to the Deal via the DealsProducts API; approval status migrates as a custom picklist field. Ploomes Quote version history is not accessible via the public API and cannot be migrated; we alert customers to this limitation during scoping and recommend capturing PDF snapshots before migration.

Ploomes Orders are generated from Deals and reference Products. We migrate Order data by identifying Ploomes Deals in a closed-won stage, linking the associated Products to the Pipedrive Deal, and preserving order totals and line items. API pagination for Orders is capped at 300 records per request; chunked extraction loops handle large order histories. Order number and order date migrate as custom fields on the Pipedrive Deal.

Ploomes Tasks map to Pipedrive Activities with type, title, due date, owner, completion status, and task type preserved. Activity type (call, meeting, task) maps to Pipedrive Activity sub-types. API pagination for Tasks is capped at 300 records; we implement cursor-based or page-based pagination loops to extract all task records. Owner assignment resolves by email match to Pipedrive Users.

Tags are a flat tagging system in Ploomes applied across Contacts, Deals, and Companies. Tags migrate as Pipedrive Tags with the same names. Tag associations per record (which Contacts, Deals, and Organizations carry which tags) are preserved by creating tag assignments during the respective object migration phase.

Ploomes Users represent team members with roles and profiles. We extract user name, email, role, and team assignments. User migration is a prerequisite for Deal, Task, and Activity migration because OwnerId references must resolve to existing Pipedrive Users. Any Ploomes User without a matching Pipedrive User email is held in a reconciliation queue for the customer admin to provision before record import continues.

Ploomes Custom Fields created via POST /Fields migrate as Pipedrive custom fields on the corresponding object (People, Organizations, Deals, Activities). Field type mapping handles text, number, date, picklist, and boolean types. Pipedrive Growth tier and above supports custom fields; we verify the destination Pipedrive plan during scoping. Custom field values per record migrate during the respective object migration phase.

Ploomes Custom Objects have no direct Pipedrive equivalent. Pipedrive does not support custom objects at any tier; only custom fields on the four core objects (People, Organizations, Deals, Activities). If Ploomes migration includes custom objects, we redesign the data model by distributing custom object fields across relevant Pipedrive core objects as custom fields, with lookup relationships replaced by text fields or association tables maintained in a separate sheet for admin reference. This architectural change is documented during scoping and validated in a test migration before production cutover.