Migrate from Planports CRM to Salesforce Sales Cloud

Planports Leads (captured from Meta Instant Forms, Google Ads, TikTok, and web forms) migrate to Salesforce Lead with full source attribution preserved. The Planports lead assignment rules and status field map to Salesforce Lead Status picklist values. We create a custom field lead_source_system__c to store the original ad platform attribution (Meta_Instant_Form, Google_Ads, TikTok) for reporting continuity. If any Planports Leads have already been converted to Planports Contacts, we route them through the Lead-Contact split logic before loading into Salesforce.

Planports Contact records map to Salesforce Contact with standard fields (FirstName, LastName, Email, Phone, Title) preserved. The Contact card's WhatsApp conversation metadata (channel phone number, last message timestamp, message count) migrates to custom Contact fields whatsapp_channel__c, whatsapp_last_message_date__c, and whatsapp_message_count__c. Full message body exportability is tested during data audit; if Meta does not expose the full thread via Planports API, we document the limitation and advise re-authorizing WhatsApp Business API in Salesforce.

Planports does not have a standalone Account object; the Company name lives as a text field on the Contact record. We deduplicate all distinct Company values across Contact records, create Salesforce Account records for each unique Company name, and then link the Contact records to their parent Account by AccountId lookup. This produces a normalized Account-Contact hierarchy that mirrors Salesforce's standard data model and enables Account-level reporting. Any industry-specific Company data (property IDs for real estate, clinic IDs for health tourism) migrates to custom Account fields.

Planports Deals map to Salesforce Opportunity. Each Planports pipeline becomes a Salesforce Record Type on Opportunity, and the Planports deal stages map to Salesforce StageName values within a corresponding Sales Process. Stage probability percentages migrate to StageProbability on each StageName entry. We create the Record Type, Sales Process, and stage entries in the destination org's schema before migration begins. Any closed-lost or closed-won reasons stored as custom fields on the Planports Deal migrate to Salesforce Loss Reason or Win Reason fields.

Planports Quotes (linked to Deals with line items, pricing, and approval status) map to Salesforce Quote, which is available as a standard object from Salesforce Sales Cloud Professional tier. Quote line items map to QuoteLineItem with PricebookEntry and Product2 references resolved at migration time. Approval status (pending, approved, rejected) migrates to Salesforce Quote Status. Note that Salesforce Quote requires the Salesforce CPQ or Sales Agreement add-on to activate the Quote object on some editions; we confirm Quote availability during scoping and include CPQ activation as a pre-migration configuration step if required.

Planports Orders (post-sale records with line items, quantities, and status) map to Salesforce Order. The Order-Contract relationship in Salesforce requires an active Contract record; we create a minimal Contract record for each Order during migration to satisfy the Salesforce foreign key. If the customer does not use Salesforce Order Management or CPQ, we document the Order migration as-is and advise that financial settlement data may require a separate accounting system sync rather than native Salesforce accounting.

Planports Activity records (calls, emails, meetings, manual tasks, and notes logged against Contact or Deal records) migrate to Salesforce Task and Event objects. Calls map to Task with TaskSubtype=Call and CallDurationInSeconds preserved in a custom field. Emails map to Salesforce EmailMessage (the message content) linked to a Task record (the activity timeline entry) with WhoId pointing to the Contact or Lead and WhatId pointing to the related Opportunity or Account. Meeting records map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. We resolve parent-record lookups (ContactId, LeadId, OpportunityId, AccountId) at migration time using the deduplicated Account and Contact mapping.

Planports Notes migrate to Salesforce Note records linked via ContentDocumentLink to the parent Contact, Account, or Opportunity. Note body (rich text) migrates as-is with any embedded image attachments preserved as separate ContentDocument records. We verify that the migration user's profile has the Create Notes and Attachments permission and that the Notes without Activities setting is correctly scoped in the destination org before migration begins.

Planports Process boards track sales and marketing workflows across custom Kanban stages. We split Process board cards into two categories: sales-process cards (linked to Deals) migrate to Salesforce Opportunity records within the appropriate Record Type and Stage; service or project-process cards migrate to Salesforce Case records with a custom Case Type field identifying the original Process board source. Conditional automation rules attached to Kanban column transitions do not migrate; we document them as part of the automation rebuild inventory delivered post-migration.

Planports custom fields on Leads, Contacts, and Deals are audited during pre-migration data review and mapped to Salesforce custom fields of equivalent type. Health tourism custom fields (referral source, treatment package, clinic ID) map to custom fields on Contact and Opportunity with appropriate field-level security profiles. Real estate custom fields (property ID, viewing schedule, agent assignment) map to custom fields on Account or Opportunity depending on whether the data pertains to the property or the deal. Digital agency custom fields (campaign ID, ad spend, channel attribution) map to custom Opportunity fields. Each custom field is pre-created in the Salesforce org's schema with the correct type, length, and picklist values before the data load phase begins.

Planports User records, team roles, and deal ownership assignments migrate as relational keys against Salesforce User records. We resolve owners by email match against the destination Salesforce org's User table. Any Planports Owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Planports deal ownership (rep attribution on Deals) migrates to Salesforce Opportunity OwnerId with the original rep name preserved in a custom Opportunity field original_owner__c for audit purposes.

Files uploaded to Planports Contact or Deal cards migrate as Salesforce ContentDocument records attached via ContentDocumentLink to the parent Contact, Account, or Opportunity. Bulk attachment migration requires Planports API access (the $62/month paid add-on); if API is not available, we export files individually per record from the Planports interface and batch-upload them to Salesforce via the Bulk API. We test attachment extraction during the data audit phase and flag any size or format limitations before production migration.