Migrate your Ploomes CRM data

Ploomes Contacts include standard fields plus CNPJ/CPF identification fields native to Brazilian business records. We migrate all Contact properties including Custom Fields created via POST /Fields. API pagination is capped at 300 records per request, so large contact lists require multi-page extraction.

Companies are a distinct object from Contacts in Ploomes. We preserve the Company-Contact associations and any Custom Fields attached to the Company record. Useful for account-based selling setups.

Deals are the core pipeline object, linked to Pipeline Stages. We preserve deal value, stage history, owner assignment, and custom properties. Bulk exports are subject to the 300-item API pagination cap.

Ploomes organizes Deals into Pipeline Stages. We migrate stage names, order, and custom stage properties. Stage assignments on Deals are preserved via the deal-stage relationship.

Products have a hierarchy (Groups and Parts) and can be linked to Deals and Quotes. We export the full product hierarchy and product-custom field associations. The product database supports spreadsheet import/export via the UI for bulk updates.

Quotes are generated from Deals and reference Products with pricing. We migrate Quote line items, totals, approval status, and custom quote properties. Version history of quotes is not directly accessible via API and requires separate handling.

Tasks are activity records linked to Contacts or Deals. We migrate task titles, due dates, owners, completion status, and task types. API pagination is capped at 300 records.

Tags are a flat tagging system applied across Contacts, Deals, and Companies. We preserve tag names and associations. Tags do not have a hierarchy in Ploomes.

Users represent team members with roles and profiles. We migrate user name, email, role, and team assignments. Only admin users can create API integration keys, so we require admin-level access to the Ploomes account during migration scoping.

Teams group Users and are used for task assignment and permission scoping. We preserve team structure and team membership.

Custom Fields are created via the API using POST /Fields and are referenced by their Key property. We export all custom field definitions and their values for each record. Field types include text, number, date, dropdown, and currency. We map custom fields to equivalent destination properties or create new ones as needed.

Workflows define automated rules, SLAs, checklists, and approval flows. Workflow definitions are not directly exported via the public API. We document workflow logic during the discovery phase and recommend manual reconfiguration in the destination system or custom integration build.

Orders are generated from Deals and reference Products. We migrate order headers, line items, and totals. API pagination is capped at 300 records per request.

Attachments linked to Contacts, Deals, or Quotes are stored separately and may require separate API calls per object. We attempt to export attachments where accessible via the API and preserve file metadata. Large attachments or high-volume attachment sets require additional extraction passes.