Migrate from PlanPlus Online to Pipedrive

PlanPlus Online Contact records map to Pipedrive Person. Standard fields (name, email, phone, address) map directly. We preserve Franklin Covey priority tags and goal associations as custom fields on the Person record. Sync connections (Google, Outlook) do not carry over; we document which external systems were connected so the customer can re-authenticate OAuth links in Pipedrive after migration.

PlanPlus Online Company records map to Pipedrive Organization. Company name, industry, size, and associated contacts migrate directly. The link between Contact and Company is maintained via a lookup mapping table during import so that each Person record is associated with its correct Organization by company name match.

PlanPlus Online deals from the External Opportunity Portal map to Pipedrive Deals. Stage names from PlanPlus Online (Appointment Scheduled, Proposal Sent, Negotiation, Closed Won, Closed Lost) map to Pipedrive Stages, which we configure in the destination Pipeline before migration. Deal value, close date, and owner assignment transfer directly. We flag any PlanPlus Online deal without a linked Contact or Company for manual review before import to prevent orphaned records.

Each PlanPlus Online pipeline in Business Edition becomes a Pipedrive Pipeline with Stages that match the original stage names. We pre-create the Pipeline and Stages in Pipedrive before any Deal import so that the stage reference is satisfied at the moment of insert. Probability percentages from PlanPlus Online migrate to Pipedrive Stage probability settings.

PlanPlus Online calendar events including appointments and all-day events migrate as Pipedrive Activities with type Meeting. Start and end times, location, and linked attendees transfer. We check time-zone settings during pre-migration audit and normalize to UTC before import to prevent calendar drift. Linked tasks or projects map to separate Task Activities.

PlanPlus Online tasks migrate as Pipedrive Activities with type Task. Priority, due date, status, and assignment transfer. Subtasks map as child activities linked to the parent Task. Franklin Covey priority quadrants (A1, A2, A3, B1, B2, B3, C1, C2, C3) transfer as a custom field on the Activity if present; otherwise they are preserved in a text custom field for the customer to configure as a picklist in Pipedrive.

PlanPlus Online Projects (Business Edition) present a structural challenge because Pipedrive has no native Project object. We offer two approaches: either create a separate Pipedrive Pipeline with a Project stage group to represent project status tracking, or migrate the project summary as a Note on the associated Deal with milestones captured as Tasks. The customer chooses during scoping. Project Summary Reports published as webpages are captured as static HTML files for manual re-upload to a file storage tool.

Custom fields from PlanPlus Online export as flat key-value pairs. We create matching custom fields in Pipedrive (custom fields on Person, Organization, and Deal) before migration, with types mapped (text to text, date to date, number to number, dropdown to picklist). Any custom fields with no direct Pipedrive equivalent are flagged for manual review and stored as text fields with the original label for the customer to re-type as a proper picklist post-migration.

PlanPlus Online user accounts map to Pipedrive User records. We match by email address. Inactive users in PlanPlus Online are flagged for the customer to decide whether to provision them as inactive Pipedrive Users (for historical attribution) or exclude them from user provisioning and reassign their records to an active owner before migration.

PlanPlus Online support tickets export with status, description, and linked contact. Pipedrive does not have a native helpdesk object in Sales CRM tiers. We map tickets as Lead records with a custom field ticket_status__c and ticket_description__c, or we map them to Pipedrive Activities linked to the associated Person. The customer chooses the approach during scoping. If Service Cloud is in scope, that is a separate migration engagement.