Migrate from Ploomes CRM to Salesforce Sales Cloud

Ploomes Contacts with Lifecycle Stage indicating unqualified or early-stage prospects map to Salesforce Lead. Contacts with qualified stages (Opportunity, Customer) map to Salesforce Contact tied to a parent Account. We compute the split at migration time using the lifecycle_stage property, preserve the original stage value in a custom field for audit, and resolve the AccountId lookup before Contact insert by matching the associated Ploomes Company to its migrated Account record.

Ploomes Company records map directly to Salesforce Account. CNPJ and CPF identification fields stored on the Company migrate to custom fields CNPJ__c and CPF__c on Account that we create before the migration phase begins. The Account-Contact association is preserved through the company-contact relationship, and we resolve the lookup at Contact insert time using Account.Name as the dedupe key.

Ploomes Deals map to Salesforce Opportunity. The dealstage property maps to StageName, and Ploomes pipeline assignment maps to a Salesforce Record Type and Sales Process that we configure in the destination org before migration. Closed-Won and Closed-Lost outcomes and any custom deal properties (including win/loss notes stored as custom fields) migrate to corresponding Opportunity custom fields.

Each Ploomes pipeline becomes a Salesforce Record Type with a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages migrate from Ploomes to Salesforce StageProbability, rounded to the nearest integer since Salesforce requires whole-number probability values. We configure all stages before Deal migration to ensure StageName references resolve on insert.

Ploomes Products map to Salesforce Product2 records with Standard Price Book entries created during import. Product hierarchy (Groups and Parts in Ploomes) maps to the Product2 family hierarchy. Product custom fields migrate to Product2 custom fields of matching type. Standard Price Book entries are created alongside Product2 records before any Line Item migration begins.

Ploomes Quotes generate from Deals and reference Products with pricing. We migrate Quote line items, totals, approval status, and custom quote properties to the Salesforce Quote object, which is standard from Professional tier. Quote PDFs and signed documents migrate as ContentDocument records attached to the Quote via ContentDocumentLink. Quote version history is not accessible via the Ploomes public API; we alert customers to manually export PDF snapshots of prior versions before the migration window and document this in the migration handoff checklist.

Ploomes Tasks map to Salesforce Task with title, due date, owner assignment, completion status, and task type preserved. Task assignments migrate by resolving the Ploomes owner reference to Salesforce OwnerId via the User mapping. Because Ploomes API pagination is capped at 300 records per request, we implement chunking loops across all Task exports and use Salesforce Bulk API 2.0 for volumes exceeding 50,000 records.

Ploomes Tags are a flat tagging system applied across Contacts, Deals, and Companies with no hierarchy. Salesforce has no native equivalent; we map tag usage to either a Multi-Select Picklist custom field (for a single-tag-per-record model) or a custom Tag__c object with a junction table (for many-to-many tag assignment). The customer selects the strategy during scoping, and we apply it consistently across all tagged records during migration.

Ploomes Users represent team members with roles and team assignments. We resolve by email match against the Salesforce destination org User table. Any Ploomes User without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role and team membership from Ploomes are documented in the migration output for manual assignment in Salesforce profiles and permission sets.

Ploomes Teams group Users for task assignment and permission scoping. Salesforce Groups and Public Groups provide a partial equivalent but do not carry the same task-routing semantics. We preserve team structure and membership names in the migration output and recommend the customer configure Salesforce Groups and Territory Management during Salesforce setup. This is documented as a configuration step rather than an API-based migration.

Ploomes Custom Fields created via POST /Fields are exported with their Key property, data type, and all values per record. We pre-create the Salesforce custom fields before data migration begins, matching Ploomes field types to Salesforce field types (text to Text, number to Number, date to Date, picklist to Picklist or Multi-Select Picklist). Custom field naming follows Salesforce __c convention. We create all custom fields in the destination Sandbox org first for validation before production migration.

Ploomes Workflows define automated rules, SLAs, checklists, and approval flows. Workflow definitions are not accessible through the documented public REST API at api2.ploomes.com. We document active workflow logic during the discovery phase (trigger conditions, actions, delays, and recipients) and deliver a written Workflow audit checklist with a recommended Salesforce Flow equivalent for each rule. The customer's admin or a Salesforce partner rebuilds the automations post-migration. This is a documentation step, not an API migration.

Ploomes Orders are generated from Deals and reference Products with line items. Salesforce has no standard Order object in Sales Cloud base (Order Management is a Service Cloud or Commerce Cloud feature). We map Ploomes Orders to Opportunity records in a Closed-Won stage with custom fields capturing order metadata (order number, payment terms, fulfillment status) and line items mapped to OpportunityLineItem. We flag this during scoping and recommend the customer decide whether to include order metadata as custom fields on the closed Opportunity or to handle order management separately in an OMS.

Attachments linked to Ploomes Contacts, Deals, or Quotes are stored separately and require separate API calls per object. We export attachment metadata (filename, MIME type, linked object, linked object ID) and attempt to retrieve file content via the Ploomes attachment endpoint where accessible. Files migrate as Salesforce ContentVersion records with ContentDocumentLink records linking them to the parent Account, Contact, or Opportunity. If the Ploomes API does not expose attachment file content directly, we document the attachment list in the migration output for manual re-upload.