Migrate from Ploomes CRM to HighLevel

Ploomes Contacts map to GoHighLevel Contacts. Standard fields (name, email, phone, address) transfer directly. Brazilian CNPJ (corporate tax ID) and CPF (individual tax ID) fields from Ploomes migrate as custom fields on GoHighLevel Contact (e.g., custom_cnpj__c, custom_cpf__c) that the customer's GoHighLevel admin defines before import. Tag associations on Contacts migrate to GoHighLevel Contact Tags. Contact ownership (HubSpot-style Owner field) maps to GoHighLevel Assigned To on the Contact record.

Ploomes Companies are a distinct object; GoHighLevel does not have a separate Account/Company object—company information lives in the Contact record's Company Info section. We extract Company name, CNPJ, address, and industry from Ploomes Company and write them into the corresponding Contact record's company fields. This means each unique Company becomes a Contact record; if multiple Contacts share the same Ploomes Company, we deduplicate by creating one Contact with company info and linking others via a custom company_id__c field. The customer chooses the deduplication strategy during scoping.

Ploomes Deals map to GoHighLevel Opportunities. Deal value, stage, owner, expected close date, and custom fields transfer directly. Ploomes Pipeline Stages map to GoHighLevel Pipeline Stages; we configure the destination pipeline in GoHighLevel during schema design so that stage names and probabilities match. Deal-Contact associations migrate as Opportunity-Contact relationships in GoHighLevel.

Ploomes Pipeline Stages (names, order, probabilities) map to GoHighLevel Pipeline Stages. We create the GoHighLevel pipeline structure during the schema phase before any Opportunity import, preserving stage names and win/loss status indicators. Stage order in Ploomes becomes the stage sequence in GoHighLevel.

Ploomes Products with Groups and Parts hierarchy map to GoHighLevel Products. Product name, code, price, and custom fields transfer directly. GoHighLevel Products use a flat structure; if the customer uses Ploomes product groups for pricing segmentation, we create separate Products in GoHighLevel with naming conventions that preserve the group context (e.g., Group Name: Product Name). Products must exist in GoHighLevel before any Opportunity line item import.

Ploomes Quotes are a complex object with version history, approval status, and PDF attachments. GoHighLevel does not have a native Quote object with versioning. We migrate Quote line items as Opportunity line items with pricing from the most recent Quote revision. We document Quote version count per Deal during scoping and flag that prior revisions are not accessible via Ploomes API—customers who need quote history must manually export PDF snapshots before migration. Quote approval status migrates as a custom picklist field on the Opportunity.

Ploomes Tasks linked to Contacts or Deals migrate to GoHighLevel Tasks. Task title, due date, owner, status (Open/Completed), task type, and notes transfer directly. Task associations (linked Contact or Opportunity) resolve via external ID lookup during import. Ploomes API pagination is capped at 300 records per request; we chunk Task exports using cursor pagination across all Task endpoints.

Ploomes Tags applied across Contacts, Deals, and Companies migrate as GoHighLevel Tags. Tag names transfer directly; GoHighLevel Tags are a flat system applied across contacts and opportunities. We extract all unique tag names from Ploomes Contacts and Deals during scoping and create matching tags in GoHighLevel before record import so that tag associations apply immediately on insert.