Migrate from Planports CRM to HubSpot

Planports contacts map directly to HubSpot contacts. Both use a flat properties model where first name, last name, email, phone, and job title are standard fields. Owner assignment resolves by email match to existing HubSpot users. Contacts without a linked company in Planports land as standalone HubSpot contacts.

Planports company records map to HubSpot companies 1:1. Company name, domain/website, industry, employee count, and annual revenue transfer as HubSpot company properties. Parent-child company hierarchies in Planports map using HubSpot's parent company association. The mapping also ensures that all associated contacts inherit the correct company relationship, and any custom properties on the company record transfer as HubSpot custom properties, preserving segmentation and reporting logic.

Planports deal records map to HubSpot deals. Each Planports deal pipeline becomes a separate HubSpot pipeline object — pipeline stage names map value-by-value to HubSpot deal stage pick-list values. Deal amount, close date, owner, and associated contacts transfer directly. This one‑to‑one mapping preserves deal history and ensures that any custom fields on the deal are migrated as HubSpot custom properties, maintaining reporting continuity.

Planports does not have a native lifecycle_stage equivalent. The Planports lead-status value or the last-active workflow stage transfers as a custom pick-list property (e.g., Workflow_Stage__c) on the HubSpot contact. HubSpot's built-in lifecycle_stage property is not populated from Planports data directly — teams must define the mapping rules.

Planports activity history — logged calls, sent emails, scheduled meetings, and notes — migrates as HubSpot engagements. Original timestamps, owners, and linked contact/company associations are preserved. Activity body content transfers as engagement notes. Each engagement retains its original classification (call, email, meeting, note) and any custom metadata, ensuring that the timeline view in HubSpot reflects the full communication history without loss of context.

Planports file attachments on contact, company, or deal records re-upload to HubSpot Files. Each file re-attaches to the corresponding HubSpot record. HubSpot's 25MB per-file limit applies; files exceeding this are flagged for manual retrieval. All file metadata such as upload date, original filename, and content type are preserved, and any file size warnings are logged in the migration audit for your team to address before go‑live.

Planports custom fields on contacts migrate as HubSpot custom properties on the contact object. String, number, date, and pick-list types map directly. Multi-select pick-lists in Planports map to HubSpot multi-checkbox custom properties. Boolean flags map to HubSpot single-checkbox properties. Validation rules and required‑field constraints are not transferred; they must be re‑established in HubSpot property settings after migration.

Planports custom fields on companies migrate as HubSpot custom properties on the company object. Field-type mapping follows the same logic as contact-level custom fields — string, number, date, pick-list, and boolean types each have a HubSpot native equivalent. Any multi-select pick-lists or complex field definitions will be transferred as HubSpot multi-checkbox or text fields, and required‑field settings must be re‑applied in HubSpot after migration.

Planports custom fields on deals migrate as HubSpot custom properties on the deal object. Deal-level custom fields are particularly important for teams that track deal-specific metadata like product type, contract terms, or renewal dates. These custom properties ensure that reporting dashboards can segment deals by the specific attributes, and any required‑field constraints need to be re‑configured in HubSpot's property settings after migration.

Planports owner IDs resolve to HubSpot users by email address match. Unmatched owners are flagged before migration — teams either invite those users to HubSpot first or reassign their records to a fallback owner. No record lands without a valid HubSpot owner.

Planports invoice and order records have no direct HubSpot equivalent. We migrate invoice data as read-only custom properties on the associated deal — invoice number, invoice date, and total amount — so the financial history is visible in HubSpot without requiring a separate accounting system migration.

Planports' built-in WhatsApp Business API channel configuration does not migrate. Teams must set up a HubSpot-compatible WhatsApp integration post-migration (via Meta Business Partner, Make, or Zapier) and re-link WhatsApp message templates and phone numbers to the new HubSpot portal. After the integration is active, any existing WhatsApp conversation logs can be imported as PDF attachments to the contact timeline for historical reference.