Migrate from Planports CRM to Freshsales

Planports Leads (the primary intake object capturing from Meta Instant Forms, Google Ads, and TikTok) map directly to Freshsales Leads. Source attribution fields (utm_source, utm_medium, utm_campaign) migrate as custom fields on the Freshsales Lead record. Assignment rules from Planports are documented as a rebuild item for Freshsales Auto-assignment rules (available from Growth plan). Lead status values from Planports map to Freshsales Lead Status picklist values.

Planports Contact records (name, email, phone, company, WhatsApp conversation metadata) map to Freshsales Contacts. Phone numbers migrate with country code standardization. WhatsApp conversation message bodies may not export cleanly from Meta's infrastructure; we document this limitation and advise re-authorizing the WhatsApp Business API channel in Freshsales post-migration to establish fresh conversation continuity. Any Planports contact-level custom fields (e.g., health tourism referral source, real estate property ID) map to Freshsales custom fields scoped per the contact record.

Planports Deals structured into custom vertical pipeline stages map to Freshsales Deals. We map each Planports pipeline stage to a Freshsales Deal stage value, and each distinct Planports pipeline (e.g., separate health tourism vs real estate boards) maps to a Freshsales Deal Record Type with its own stage whitelist. Stage probability percentages migrate from Planports to Freshsales. Planports Deal custom fields (treatment package, property reference, campaign ID) map to Freshsales Deal custom fields.

Planports Quotes linked to Deals migrate to Freshsales Quotes with the parent Deal resolved via the deal ID mapping. Line items from Planports Quotes migrate as Freshsales Quote Items with product name, quantity, unit price, and discount preserved. Approval workflow state on Planports Quotes is documented as a manual reconfiguration item in Freshsales (available from Growth plan).

Planports Order records migrate to Freshsales Orders with Contact and Deal lookups resolved at migration time. Order status, quantities, and totals migrate directly. Financial settlement data (payment method, transaction IDs) migrates as custom fields on the Order record; we note that accounting reconciliation should be verified against source records post-migration.

Planports Activity records (calls, emails, meetings, manual notes) migrate to Freshsales Tasks (for calls, emails, and tasks) and Events (for meetings). Timestamps, owner attribution, and linked Contact or Deal references are preserved via Freshsales task and event lookups. Notes migrate as Freshsales Notes linked to the parent Contact, Deal, or Account record. Activity type flags from Planports map to Freshsales task categories and event types.

Planports Process boards (Kanban-style workflow boards) have no direct Freshsales equivalent. We migrate Process board cards as Freshsales Tasks with a custom tag set per board name and column/stage name, preserving card content and assignment. Conditional automation rules attached to board columns do not migrate; we deliver a written Process board map for the admin to rebuild using Freshsales Workflows (Growth plan) post-migration.

Planports industry-specific custom fields (health tourism referral source and treatment package; real estate property ID and viewing schedule; digital agency campaign ID and ad spend) are audited field-by-field during pre-migration data review. Each field is typed (text, number, date, picklist, checkbox) and mapped to a Freshsales custom field of equivalent type on the corresponding object. Fields with no clear Freshsales equivalent are flagged for customer decision before migration begins.

Files attached to Planports Contact or Deal cards can be exported per record from the per-record export. Bulk attachment migration requires API access (the $62/month add-on) and may be limited by Planports plan tier. We migrate file name, URL reference, and attached-to record; file hosting continuity is subject to the export completeness test during the data audit phase.

Planports User records and deal ownership assignments migrate as relational keys. We match Planports owners by email against Freshsales Users provisioned by the customer before migration. Any Planports owner without a matching Freshsales User is held in a reconciliation queue for the customer's admin to provision. Deal and Activity ownership references are updated to the resolved Freshsales User IDs before record import.