Migrate from Planports CRM to Nutshell

Planports Contact records (name, email, phone, company, WhatsApp thread metadata) map to Nutshell People. WhatsApp conversation message body text migrates as a note attachment if the full export test succeeds; otherwise we preserve only contact metadata (contact name, timestamp, direction) and document the limitation explicitly. We deduplicate by email match before insert and resolve the linked Organization reference from the Companies import phase.

Planports Company records map directly to Nutshell Organization. The Planports company domain becomes the Organization's website field used as a dedupe key. Organization must be inserted before the related Contact import so that the Organization reference is satisfied at the moment of Person insert.

Planports Leads (from ad forms, web intake, WhatsApp inbound) map to Nutshell Leads with source attribution preserved. Lead status, assignment rules, and any lead scoring custom fields transfer as custom fields on the Nutshell Lead object. Leads that have already been converted to Contacts in Planports are migrated as Contacts only; the duplicate Lead is excluded.

Planports Deals structured into industry-specific pipeline stages (health tourism, real estate, digital agency verticals) map to Nutshell Deals. We map each Planports pipeline stage to a corresponding Nutshell Deal status, with deal amount, probability, owner, and linked Contact and Organization preserved. Stages with no direct Nutshell equivalent are flagged during the data audit for the customer to choose a mapping or a new stage name before production migration.

Planports Quotes linked to Deals with line items, pricing, and approval status map to Nutshell Quote if the destination plan includes the Nutshell Quotes tool. If the customer does not carry the Quotes add-on, Quote records migrate as notes on the related Deal with the line-item data preserved as structured text for manual rebuild. We confirm the destination plan's quoting capability during scoping.

Planports Orders with line items, quantities, financial settlement, and status have no direct Nutshell equivalent because Nutshell does not include a native order management or accounting layer. We migrate Order records as Opportunity Products attached to the linked Deal, with financial settlement data preserved as a note on the Deal for accounting re-entry post-migration. This limitation is documented explicitly in the migration scope before extraction begins.

Planports Activity records (calls, emails, meetings, tasks, manual notes) with timestamps, owner attribution, and linked Contact or Deal references map to Nutshell Activity records on the timeline. Each Activity is linked to the resolved Person or Organization using the Person/Organization IDs from the People and Organization import phase. Activity type, direction, duration, and disposition migrate as typed fields.

Planports Process Kanban boards track sales and marketing workflows across custom stages. Board columns map to Nutshell Activity tasks organized by subject, and board cards with their card-level fields migrate as individual task records linked to the relevant Person or Organization. Any conditional automation rules attached to board columns or card triggers are flagged as Planports automation configuration and do not migrate; they appear in the automation rebuild inventory we deliver post-migration.

Planports User records, team roles, and deal ownership assignments are resolved by email match against Nutshell Users. Any Planports Owner without a matching Nutshell User is placed in a reconciliation queue for the customer to provision before record import resumes. Deal ownership migrates as OwnerId references on the imported Deals. Inactive Planports users are migrated as inactive Nutshell users or excluded per the customer's preference set during scoping.

Industry-specific custom fields on Leads, Contacts, Deals, and Activities in Planports (referral sources and treatment packages in health tourism, property IDs and viewing schedules in real estate, campaign IDs and ad spend in digital agencies) are audited during the data review, mapped to Nutshell custom fields, and loaded before any record migration begins. Fields with no Nutshell equivalent are flagged in the mapping matrix for the customer to decide whether to drop, approximate with a text field, or defer. Custom field type conversion (date, number, picklist) is applied at transform time.