Migrate from Planports CRM to HighLevel

Planports Leads capture from Meta Instant Forms, Google Ads, and TikTok ads with source attribution fields. We migrate Lead records as GoHighLevel Contacts with the source attribution (e.g., meta_lead, google_ads, tiktok_ads) stored as a custom tag or source field. Any Planports lead status values are mapped to GoHighLevel Contact status or pipeline entry stages.

Planports Contact records carry standard fields (name, email, phone, company) plus WhatsApp conversation thread references. We migrate all standard fields directly. WhatsApp conversation message bodies are flagged as non-exportable from Planports; we document this limitation and advise the customer to re-authorize the WhatsApp Business API channel in GoHighLevel for forward conversation continuity.

Planports does not have a dedicated Company object; company data lives as a field on Contact. We extract company values from Contact records, deduplicate by domain or name, and create GoHighLevel Company records. Company fields (industry, size, address) are created as custom fields on the GoHighLevel Company object where no standard equivalent exists.

Planports Deals structured into industry-specific pipeline stages (health tourism treatment packages, real estate property stages, agency deal milestones) map to GoHighLevel Opportunities with stage values recreated in the GoHighLevel pipeline builder. We flag any Planports stages with no clear GoHighLevel equivalent during the data audit and present mapping options to the customer before migration.

Planports Quotes are linked to Deals and contain line items, pricing, and approval status. GoHighLevel does not have a native Quote object at the Starter tier; we migrate Quote records as Opportunity custom fields and line-item data stored in custom fields or as a linked Custom Object (Quote Lines). On the Unlimited tier, the customer can configure a Quote workflow manually after migration.

Planports Order records track post-sale items, quantities, and status linked to Contact and Deal. We migrate Order records as a GoHighLevel Custom Object with a lookup relationship to Contact and Opportunity. The customer configures the Order Custom Object schema during the GoHighLevel setup phase before migration.

Planports Process boards use a Kanban layout to track sales and marketing workflows across custom stages. Card records migrate as Custom Object entries; column headers (stages) map to a status picklist on the Custom Object. Any conditional automation rules attached to board columns do not migrate and are documented in the automation inventory for manual rebuild.

Activity records (calls, emails, meetings, manual notes) log against Contact or Deal records in Planports. We migrate activities as GoHighLevel Tasks and Notes with timestamps, owner attribution, and linked Contact or Opportunity references. Activity type maps to a GoHighLevel custom field or tag for segmentation.

Planports industry-specific custom fields (health tourism referral sources and treatment packages, real estate property IDs and viewing schedules, agency campaign IDs and ad spend) are audited during the data review phase. We produce a field mapping matrix, create equivalent custom fields in GoHighLevel (on Contact, Company, or Custom Objects as appropriate), and flag any fields with no clear destination equivalent for customer decision before migration begins.

Files uploaded to Contact or Deal cards in Planports are exported per record where accessible. Bulk attachment migration requires the Planports API add-on to be active. We migrate file references and URLs as GoHighLevel attachment records or links on the relevant Contact or Opportunity. Customers using Planports file storage directly should download attachments before migration as a precaution.