Migrate from Ploomes CRM to Microsoft Dynamics 365 Sales

Ploomes Contact records with lifecycle stage before sales qualified lead map to Dynamics 365 Lead. Lifecycle stage at sales qualified lead or beyond maps to Dynamics 365 Contact tied to an Account. We compute the split using Ploomes' lifecyclestage property at migration time and preserve the original value in a custom field ploomes_lifecycle__c on both Lead and Contact for audit and reporting continuity. Owner assignment from Ploomes resolves to Dynamics 365 OwnerId via User email match.

Ploomes Company maps to Dynamics 365 Account. CNPJ and CPF identification fields from Ploomes migrate as custom fields cnpj__c and cpf__c on Account, with validation rules applied to enforce Brazilian format (CNPJ: 14 digits, CPF: 11 digits). Account Name and Website map directly; the Company-Contact associations are preserved through the Contact split phase via the parent Account lookup.

Ploomes Deal maps to Dynamics 365 Opportunity. Deal value, close date, owner assignment, and custom deal properties migrate directly. The Ploomes pipeline maps to a Microsoft Dynamics 365 Sales Process and Record Type configured before migration. Stage probabilities migrate to StageProbability values. Lost deal reason custom properties become a Loss Reason field on Opportunity.

Ploomes pipeline stages migrate as Microsoft Dynamics 365 Sales Process stages with matching probability values. Each stage's order and SLA properties map to the corresponding stage in the configured Sales Process. Stage assignment on Deals is preserved via the Opportunity stage relationship. Custom stage colors and labels are documented as metadata for admin reconstruction.

Ploomes Products with Groups and Parts hierarchy map to Dynamics 365 Product2 records. The product hierarchy is preserved using the Family field for grouping and Description for parts details. ProductCode maps from Ploomes' sku property. Custom product properties migrate as custom fields on Product2. Standard Price Book entries are created during migration.

Ploomes Quote records migrate to Microsoft Dynamics 365 Sales Quote, preserving header totals, approval status, and line items with pricing. Quote is a standard Microsoft Dynamics 365 Sales object available from Professional tier. Quote PDFs generated in Ploomes migrate as file attachments to the Quote record. Note that Ploomes Quote version history is not accessible via the public API; only current Quote state migrates.

Ploomes Tasks migrate to Dynamics 365 Task records. Task title, due date, owner, completion status, and task type all map directly. Owner resolution uses email-based matching against the Dynamics 365 User table. Large task datasets are chunked to handle Ploomes' 300-item pagination cap per request, with cursor-based iteration across all pages.

Ploomes engagement records (calls, emails, meetings, notes) migrate to their Dynamics 365 equivalents: calls to Task with TaskSubtype=Call, emails to EmailMessage linked to an Activity Task, meetings to Event with start and end times preserved, and notes to Note records. Activity timestamps are preserved as ActivityDate. Attachments linked to engagements migrate as ContentDocument records linked to the parent activity.

Ploomes Tags are a flat tagging system applied across Contacts, Deals, and Companies. Tags migrate as multi-select picklist values on the relevant Contact, Opportunity, and Account records in Dynamics 365. We preserve all tag names and their associations during migration. If the customer has a large or redundant tag vocabulary, we recommend tag consolidation strategy during scoping.

Ploomes Custom Fields created via POST /Fields migrate to Dynamics 365 custom fields. We capture the Ploomes API Key, field type, and target object for each custom field, then provision the equivalent custom field in Dynamics 365 with matching type and add it to the appropriate forms. Field values are migrated with the parent record. Validation rules defined in Dynamics 365 are applied post-load.