Migrate from Ploomes CRM to Zoho CRM

Ploomes Contacts map directly to Zoho CRM Contacts. Standard fields (Name, Email, Phone, Address) transfer via bulk API. Brazilian CPF identification numbers stored in Ploomes' native CPF field migrate to a custom Zoho CRM single-line field (CPF__c) that we create before the Contact import phase. Custom fields created via POST /Fields in Ploomes map to equivalent Zoho CRM custom fields by type (text to text, number to number, date to date, picklist to picklist). Contact-CustomField associations preserve by importing custom field values alongside the Contact record.

Ploomes Companies map to Zoho CRM Accounts. The Company Name maps to Account Name, and the native CNPJ field maps to a custom Zoho CRM field (CNPJ__c) that we provision during schema setup. Company-Contact associations preserve through the Account-Contact lookup relationship in Zoho, which we resolve at migration time by matching Contact email addresses against the imported Account record list. Any Company-level custom fields created via POST /Fields in Ploomes translate to Zoho Account custom fields.

Ploomes Deals map to Zoho CRM Deals. The dealstage property maps to Zoho Stage, the pipeline assignment maps to a Zoho module layout or pipeline view that we configure before migration. Deal value (amount), owner, close date, and custom properties transfer directly. Ploomes Deals linked to a Company (Account) resolve to AccountId in Zoho at migration time. Deals are imported after Accounts and Contacts so that parent-record lookups are satisfied on insert.

Ploomes Pipeline Stages map to Zoho CRM Deal Stage values. We extract the full stage list from Ploomes via GET /Pipelines and configure the corresponding Stage picklist in Zoho before Deal migration begins. Stage order and probability percentages transfer to Zoho Stage configuration. If the customer uses multiple Ploomes pipelines, we map each to a separate Zoho pipeline view or module layout.

Ploomes Products with their hierarchy (Groups and Parts) map to Zoho CRM Products. The product name, SKU (hs_sku equivalent), unit price, and product-custom field associations transfer directly. Zoho Products require a Standard Price Book entry to be associated with Deals, so we create price book entries during the product import phase. If the customer's Ploomes product database uses spreadsheet uploads with pricing tiers, we replicate those tiers as Zoho Price Book entries.

Ploomes Quotes map to Zoho CRM Quotes. Quote headers, line items, totals, approval status, and custom properties transfer. The Deal-Quote relationship in Ploomes maps to the Quote-Deal lookup in Zoho. Note that Ploomes Quote version history is not accessible via the public API; we export the current state of all Quotes only and alert the customer to capture PDF snapshots of any versioned quotes before migration. Quote PDFs cannot be programmatically extracted from Ploomes and must be manually downloaded by the customer.

Ploomes Orders (generated from Deals) map to Zoho CRM SalesOrders. Order headers, line items, totals, and the Deal-Order relationship transfer. API pagination for Orders in Ploomes is capped at 300 records per request, so we implement page-based pagination loops across the Orders endpoint before bulk insertion into Zoho. The Order-Deal linkage resolves at migration time using the deal identifier as an external reference.

Ploomes Tasks map to Zoho CRM Tasks. Task title, due date, owner, completion status, and task type transfer directly. Ploomes Tasks linked to Contacts or Deals resolve to the corresponding Zoho Contact or Deal ID via the email and deal identifier lookup tables created during earlier migration phases. Tasks are imported after Contacts and Deals to satisfy the activity-parent lookups.

Ploomes Tags are a flat tagging system applied across Contacts, Deals, and Companies. Tags do not have a hierarchy in Ploomes. We migrate tags as multi-select picklist values on the corresponding Zoho CRM fields (Contacts.Tags, Deals.Tag). The customer chooses whether to map tags as multi-select picklists or as a separate Tag module in Zoho during scoping.

Ploomes Users map to Zoho CRM Users by email address match. We extract all Users from Ploomes via GET /Users during discovery, map them to Zoho User records by email, and flag any Ploomes Owner without a matching Zoho User for the customer's admin to provision before production migration. Ploomes role and team assignments map to Zoho Role and Zoho CRM Territory configurations.

Ploomes custom fields created via POST /Fields migrate as Zoho CRM custom fields. We extract all custom field definitions (field name, type, and Key property) from Ploomes and pre-create the corresponding Zoho fields during the schema design phase before any record migration begins. Field type mapping follows standard conventions (text to single-line, number to integer or decimal, date to date, checkbox to boolean). Custom fields on Deals, Contacts, Companies, and Products each require separate field creation in their respective Zoho modules.

Ploomes Workflows define automated rules, SLAs, checklists, and approval flows. These definitions are not accessible through the Ploomes public REST API. We document active workflows during discovery using a manual audit checklist that we provide to the customer, and we deliver a written workflow inventory with each rule's trigger, conditions, actions, and a Zoho Workflow Rule equivalent. The customer's Zoho admin rebuilds the automation logic in Zoho Workflow Rules post-migration. We do not migrate Workflows as code.