Migrate from Planports CRM to Microsoft Dynamics 365 Sales

Planports Contact records with no deal association and no qualified status map to Dynamics 365 Lead. Planports Contacts with active Deals, Quotes, or Orders map to Dynamics Contact with a parent Account. We resolve Account membership by checking if the Contact's company name or domain matches an existing Dynamics Account, or we create the Account first and set Contact.AccountId at import time. WhatsApp conversation references (metadata: contact, timestamp, direction) migrate as custom fields on Contact. Full message body text migrates only if Planports exports it in a machine-readable format during the data audit phase; otherwise we document the limitation and recommend WhatsApp Business API re-authorization in Dynamics via a third-party connector.

Planports Leads capture ad intake from Meta Instant Forms, Google Ads, and TikTok. Source attribution fields migrate as custom fields on Dynamics Lead (e.g., custom_leadsource_detail__c storing the ad campaign name or Meta form ID) because Dynamics' standard LeadSource picklist does not include granular Meta or TikTok values. We preserve the original Planports lead creation timestamp and any lead scoring values in custom fields.

Planports Deals map to Dynamics 365 Opportunity. Each Planports industry-specific pipeline stage maps to a Dynamics Opportunity StageName within a Sales Process we configure before migration. Planports custom Deal fields (treatment packages in health tourism, property IDs in real estate, campaign IDs in digital agencies) map to Opportunity custom fields that we create during the schema design phase. Conditional automation rules attached to Deal stage transitions do not migrate; we document them in the automation inventory for the admin to rebuild in Dynamics Sales Automation or Power Automate.

Planports Quotes linked to Deals migrate to Dynamics Quote records with QuoteLineItems. We resolve the parent Opportunity reference during import so Quote.OpportunityId is set. Quote approval status migrates as a custom field since Dynamics Quote does not have a native approval state equivalent. Quote PDFs and signed documents migrate as Notes or SharePoint file attachments linked to the Quote record.

Planports Orders migrate to Microsoft Dynamics 365 Sales Order (or Invoice depending on the customer's post-sale workflow). Order line items migrate as SalesOrderDetail records with Product2 reference resolved during import. Financial settlement data migrates as-is but we flag that customers with accounting integration needs (Dynamics 365 Business Central) should verify Chart of Accounts mapping as a separate finance-scope task outside the CRM migration.

Planports Activity records (calls, emails, meetings, tasks, notes) migrate to Dynamics Task, EmailMessage, and Note objects. Call disposition and duration migrate as custom Task fields. Meeting attendee references migrate as EventRelation records. Notes migrate as Dynamics Note attached via regarding_objectid to the parent Contact, Lead, Account, or Opportunity. Kanban card comments on Planports Process boards migrate as Note records on the related Deal or Contact; the card-to-column relationship itself does not have a native Dynamics equivalent and is documented as requiring manual re-entry or Power Automate recreation.

Planports Process boards use a Kanban layout with columns and cards. Column names map to custom picklist values on a Deal-related custom field. Card records (with their title, description, due date, and owner) migrate as Note or Task records linked to the parent Deal. Conditional automation rules attached to card triggers (move-to-column actions, auto-assignment) do not migrate; we include them in the automation inventory document. Teams relying heavily on Kanban workflow visibility should plan a Power Automate rebuild or consider Dynamics Sales Automation playbooks post-migration.

Industry-specific custom fields on Planports Leads, Contacts, and Deals (health tourism referral sources and treatment packages; real estate property IDs and viewing schedules; digital agency campaign IDs and ad spend) require field-level mapping to Dynamics custom fields on the corresponding entity. We audit every field during the pre-migration data review, produce a field mapping matrix, and create the destination custom fields with correct types (text, picklist, currency, date) before any data loads. Fields with no clear Dynamics equivalent go to a customer decision log for explicit direction before migration begins.