Migrate from Ploomes CRM to Freshsales

Ploomes Contact records map to Freshsales Lead if the contact is unqualified or has no associated Company; they map to Freshsales Contact if a Company association exists and the contact represents a qualified buyer. We use Ploomes' lifecycle stage and status properties to determine the split at migration time and preserve the original Ploomes lifecycle value in a Freshsales custom text field for audit. CNPJ/CPF values on Ploomes Contacts migrate into Freshsales custom fields that must be created before import.

Ploomes Company records map directly to Freshsales Account. The Brazilian CNPJ/CPF identification fields migrate into Freshsales custom fields (cnpj_cpf__c) created during the pre-migration schema setup phase. Account is inserted before any Contact import so that the Contact-Account Lookup relationship is satisfied at insert time. Ploomes Company custom fields map to Freshsales Account custom fields of equivalent type.

Ploomes Deals map 1:1 to Freshsales Deals. Deal value, stage, owner assignment, expected close date, and custom properties migrate directly. Ploomes pipeline stages map to Freshsales deal stage values, which we configure in Freshsales Admin before migration. Deal-Company associations migrate as Freshsales Account-Account ID lookups resolved at migration time. Note that Freshsales Deals do not have the same native SLA automation that Ploomes Workflows provide; SLA logic must be rebuilt in Freshsales Workflows post-migration.

Ploomes Quotes (generated from Deals with product references) migrate as Freshsales Deals with associated Products. The quote header (total, approval status, custom fields) becomes the Deal record; quote line items become Deal line items referencing Freshsales Products. Version history of Quotes is not accessible via Ploomes' public API, so only the current quote state migrates. We alert customers to this limitation during scoping and recommend exporting PDF snapshots before migration if prior revisions are business-critical.

Ploomes Products (with Groups and Parts hierarchy) map to Freshsales Product records. The product name, code (SKU), unit price, and custom properties migrate. The hierarchical grouping in Ploomes is flattened into Freshsales product categories or preserved as a custom field; the customer chooses the flattening strategy during scoping. Product-custom field associations migrate as Freshsales Product custom fields.

Ploomes Tasks migrate to Freshsales Tasks with title, due date, owner (resolved via email match to Freshsales User), completion status, and task type preserved. Tasks linked to Deals resolve the WhatId to the migrated Freshsales Deal ID. Tasks linked to Contacts resolve the WhoId to the migrated Freshsales Contact or Lead. API pagination for Tasks is capped at 300 records per Ploomes request, so we implement cursor-based pagination loops across all Task exports to avoid truncation.

Ploomes Tags are a flat tagging system applied across Contacts, Deals, and Companies. We migrate tag names and their associations as Freshsales custom multi-select fields on the corresponding object (contact_tag__c, deal_tag__c, account_tag__c). Freshsales does not have a native cross-object tag taxonomy, so the flat tag structure is decomposed into object-specific custom fields. The customer selects the field names and valid values during scoping.

Ploomes Users map to Freshsales Users by email match. We extract every distinct Owner referenced on Contact, Company, Deal, and Task and reconcile against the Freshsales User table. Any Ploomes Owner without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Note that only Ploomes admin users can create API integration keys, so we require admin-level access to the Ploomes account at migration kickoff.

Ploomes Custom Fields created via POST /Fields migrate to Freshsales custom fields of the equivalent type (text, number, date, picklist, checkbox, etc.). We export all custom field definitions and their values for each record during the transform phase. CNPJ/CPF fields are mapped to Freshsales text custom fields rather than any native field type because Freshsales does not include Brazilian business ID validation natively.

Ploomes Orders (generated from Deals and referencing Products) migrate as Freshsales Deals with line items. The order header (totals, status, custom fields) becomes the Deal record; order line items become Deal line items referencing migrated Products. API pagination for Orders is capped at 300 records per request, requiring the same chunking strategy used for Contacts and Tasks.