Migrate from PlanPlus Online to Salesforce Sales Cloud

PlanPlus Online Contacts map directly to Salesforce Contact. Standard fields (Name, Email, Phone, Title, Mailing Address) migrate via CSV column mapping. We preserve Franklin Covey priority quadrant tags (if configured as a custom property) in a custom field fc_priority_quadrant__c. Sync connector metadata does not migrate; we document which external systems were connected so the customer reconfigures post-migration.

PlanPlus Online Company records map to Salesforce Account. Company name becomes Account Name; industry, size, and billing address map to equivalent fields. Links between Contacts and Companies are maintained via a mapping table during import so that AccountId is resolved on each Contact before insert. Mission statements and goal hierarchies stored as Company custom properties migrate to custom Account fields.

PlanPlus Online Deals tracked in the External Opportunity Portal map to Salesforce Opportunity. Stage names, deal values, close dates, and associated contact references migrate via CSV. We create Salesforce Opportunity Stages in the destination org to match the source stage names, with probability percentages carried over. External Deal IDs are preserved in a custom field pp_deal_id__c for reconciliation.

Calendar events including appointments and all-day events export via sync connector CSV. We preserve StartDateTime, EndDateTime, Location, and linked contact references. Time zone settings are normalized during the pre-migration audit because PlanPlus Online documentation requires correct time zone configuration to prevent calendar drift. EventRelation records are created to link attendees to the migrated Event in Salesforce.

Tasks migrate with Priority, DueDate, Status, and assignment. Subtasks map as child Task records with a ParentTaskId reference. Franklin Covey priority quadrants preserved as fc_priority_quadrant__c on Task. Linked tasks referencing Contacts or Deals resolve via the contact mapping table and the opportunity mapping table respectively before insert.

PlanPlus Online Projects export with status, milestones, and task breakdowns. We create a Salesforce custom object Project__c to receive project records, including status, description, and external project ID preserved in pp_project_id__c. Project Summary Reports published as webpages capture as static HTML attachments linked via ContentDocumentLink. Cross-project dependencies are stored as text fields because Project__c does not natively support dependency graphs.

Custom fields created in PlanPlus Online export as flat key-value pairs. We map each to an equivalent Salesforce custom field of matching type (text, number, date, picklist). Fields with no direct Salesforce equivalent are flagged for manual review during the sandbox validation phase. The customer decides whether to keep or archive unmapped custom fields.

PlanPlus Online user accounts map to Salesforce User records by email match. User display name, email, and role migrate. Inactive users are flagged for the customer to decide whether to provision them as inactive Salesforce Users. OwnerId on Contact, Account, and Opportunity is resolved via this lookup before record import.

Sync connections to Google, Microsoft 365, and Outlook are authentication configurations that do not carry over to Salesforce. We document which external systems were connected, the sync direction, and the last sync timestamp so the customer reestablishes connections using Salesforce's native Outlook integration and Google sync after migration.

FAQs managed in the PlanPlus Online Support Portal export as article records. We map article title, body content, and category to Salesforce Knowledge ArticleVersion and ArticleType. Active status migrates as PublishStatus on the Salesforce article. FAQs are delivered as a written import file for the customer's Salesforce admin to load via Knowledge API.

Help desk tickets export with status, description, linked contact, and creation timestamp. We map ticket status to Salesforce Case Status, description to Case Description, and contact reference to ContactId on Case. Closed tickets migrate as historical records; open tickets are flagged for the customer to re-open manually post-migration if required.

Form data captured via PlanPlus Online contact forms and landing pages exports as Contact records with a Form_Source__c custom property set to the landing page name. Submission timestamps and custom form field responses preserve as custom fields on the migrated record. The customer decides whether to treat form submissions as Leads (unqualified) or Contacts (qualified) based on their sales process.