Migrate from Planports CRM to Twenty CRM

Planports Leads (primary intake from Meta Instant Forms, Google Ads, TikTok, and web forms) map to Twenty People records. Source attribution fields (utm_source, utm_medium, utm_campaign) migrate as custom fields on People. Lead status and assignment rules preserve as custom fields. We compute a lifecyclestage__c custom field from Planports lead status so the customer can reconstruct segmentation in Twenty after migration.

Planports Contact records map to Twenty People. Standard fields (name, email, phone, company) migrate directly. WhatsApp conversation metadata (contact, timestamp, direction, message count) migrates as custom fields on the People record. Full message body text may not export cleanly from Meta's infrastructure; we document this limitation during the data audit and advise the customer to re-authorize their WhatsApp Business API channel in Twenty post-migration if conversation history continuity is required.

Planports Companies map to Twenty Company records. Domain from Planports becomes the Company website field and is used as the dedupe key during import. Company is created before any People import so that the relationship lookup is satisfied at the moment of People insert.

Planports Deals map to Twenty Opportunities. Each Deal pipeline stage maps to a Twenty Opportunity stage that we configure before migration. Closed-Won and Closed-Lost reasons from Planports custom properties become Opportunity custom fields. Deal amount, expected close date, and owner assignment migrate directly.

Planports custom pipeline stages per industry vertical (health tourism, real estate, digital agencies) map to Twenty Opportunity stage values. We configure each stage in Settings → Data Model before migration, preserving the stage order and probability percentage from Planports. Industry-specific stage labels (e.g., treatment package, property viewing, campaign launch) become custom field picklist values rather than native stage names to avoid conflicts with the standard Twenty stage model.

Planports Process boards are Kanban-based workflow cards without a direct Twenty equivalent. We map each Process card to a Twenty Opportunity record with custom fields capturing the board name, column/stage, card position, and any conditional metadata from the Planports Process. The customer rebuilds the Kanban view manually in Twenty's Opportunities board. Automation rules attached to Process columns do not migrate; we document them in the automation inventory for manual rebuild.

Planports Quotes (line items with pricing and approval status linked to Deals) map to Twenty Note records with custom fields for line items, pricing, and approval state, or to a custom Quote object if the customer requests it during scoping. We preserve the Quote-to-Deal relationship by setting the Opportunity (Twenty) reference to the migrated Deal. Approval workflow state migrates as a custom field rather than an active workflow.

Planports Order records (post-sale items, quantities, status linked to Contact and Deal) map to a custom Order object in Twenty or to Note records with custom fields, depending on the customer's reporting needs. We preserve the Contact and Deal references during migration. Financial settlement data may require accounting system reconciliation post-migration.

Planports Activity records (calls, emails, meetings, tasks, manual notes) map to Twenty Task and Note records. Call disposition and duration migrate as custom Task fields. Meeting start/end times and location preserve on Task records. Activity timestamps preserve for timeline ordering. Owner attribution migrates by resolving the Planports owner reference to the migrated Twenty user.

Industry-specific custom fields on Leads, Contacts, and Deals (health tourism referral sources and treatment packages; real estate property IDs and viewing schedules; digital agency campaign IDs and ad spend) require field-level mapping. Planports does not publish a public schema, so we audit field names and types from the exported data during the pre-migration review. All custom fields must be created in Twenty Settings → Data Model before CSV import because Twenty's import creates records, not fields. We produce a field mapping matrix and flag any Planports fields with no clear Twenty equivalent for customer decision before migration begins.

Files uploaded to Contact or Deal cards can be exported individually per record from Planports. Bulk attachment migration requires active API key access and may be limited by Planports plan tier. We migrate file references (file name, upload date, uploader) as URL fields on the migrated Twenty record. The customer uploads the actual files to Twenty's file storage or a linked cloud storage service post-migration.

Planports User records and deal ownership assignments migrate as Twenty WorkspaceMember records. We resolve owners by email match. Planports requires a minimum of 3 users on all plans, which affects per-user cost calculations. Twenty requires all referenced users to be invited and active before importing records with Owner or Assignee assignments; any Planports owner without a matching Twenty user goes to a reconciliation queue for the customer's admin to provision before record import resumes.