Migrate from Planports CRM to Pipedrive

Planports Leads map directly to Pipedrive Leads. The source attribution fields (Meta Instant Form, Google Ads, TikTok) migrate to Pipedrive's Lead source field, with ad campaign identifiers stored in custom Lead fields. Owner assignment migrates by email match against Pipedrive Users. We flag any Leads without a matching Pipedrive User for admin provisioning before production migration.

Planports Contact records migrate to Pipedrive Contacts with name, email, phone, and company preserved. WhatsApp conversation history stored in Meta infrastructure is tested for exportability during the data audit phase; where full message bodies cannot be extracted, we document the limitation and recommend re-authorizing WhatsApp Business API in Pipedrive's marketplace post-migration. Standard contact fields and custom fields migrate directly.

Planports Company records map to Pipedrive Organizations. Company domain, industry, size, and address fields migrate to the equivalent Pipedrive Organization fields. Organization is created before any Contact import so that the Organization reference is resolved at the moment of Contact insert. Owner migrates by email match.

Planports Deals map to Pipedrive Deals with the pipeline stage and deal value preserved. Industry-specific stages (health tourism referral stages, real estate property stages, digital agency campaign stages) are mapped to Pipedrive pipeline stages that we configure before migration. Lost and won reasons migrate as custom Deal fields. Deal owner migrates by email match to Pipedrive User.

Each Planports Deal pipeline becomes a Pipedrive Pipeline with custom Stage values. We create the destination pipeline structure during workspace setup, mapping Planports stage names and probabilities to Pipedrive stages and probability percentages. Industry-specific stage labels (treatment package stages, property viewing stages, campaign milestone stages) are preserved as stage names in the configured Pipedrive pipeline.

Planports Quotes contain line items, pricing, quantities, and approval status linked to a Deal. Pipedrive does not have a native Quote object on all tiers; we map Quotes to Deals with line items stored as Deal Product entries or as structured custom fields on the Deal record. Approval status migrates as a custom Deal field. Customers needing full Quote object functionality require Pipedrive's Sales tool add-on.

Planports Orders track post-sale items, quantities, and fulfillment status. We map Order records to Pipedrive Deals with a custom order status field (Pending, Shipped, Delivered, Cancelled) and order line item details stored in Deal custom fields or as Deal Product entries. Settlement and financial data that belongs in an accounting system is flagged for customer review and excluded from the CRM migration scope.

Planports Activities (calls, emails, meetings, manual tasks) migrate to Pipedrive Activities with type, timestamp, owner, and linked entity preserved. Call duration and disposition migrate to custom Activity fields. Meeting attendees link to the associated Contact or Deal. Email content migrates as Activity body text. Notes migrate as Activity records with type NOTE.

Planports Process Kanban boards have no direct Pipedrive equivalent. We translate board columns to Pipedrive pipeline stages and card records to Deals or Activities with custom fields capturing the board card data. Conditional automation rules attached to Process board columns do not migrate; we document every Process board in the automation inventory deliverable for the customer's admin to rebuild as Pipedrive workflow rules post-migration.

Files uploaded to Planports Contact or Deal cards are exported per record. We attach these as Files linked to the migrated Contact, Deal, or Organization record in Pipedrive. Bulk attachment migration requires API access and may be limited by Planports plan tier. We test attachment exportability during the data audit and flag any Planports plan-tier constraints before production migration.

Planports User records and deal ownership assignments migrate as relational keys resolved by email match against Pipedrive Users. Team roles and deal ownership attribution are preserved. Owners without a matching Pipedrive User go to a reconciliation queue for admin provisioning before record import resumes.