Migrate from Planports CRM to Zoho CRM

Planports Leads are the primary intake object capturing from Meta Instant Forms, Google Ads, TikTok, and web forms with source attribution. They map directly to Zoho CRM Leads. The Planports lead status, assignment rules, and source attribution properties migrate to Zoho Lead Status, Owner, and Lead Source fields respectively. If the Planports account uses a lead scoring custom field, we create a corresponding numeric field in Zoho Leads during schema design.

Planports Contact records carry name, email, phone, and company fields plus the WhatsApp conversation thread reference stored per card. We migrate Contact records to Zoho Contacts in a 1:1 mapping. WhatsApp conversation metadata (contact, timestamp, direction) migrates to Zoho as custom fields or linked Notes; full message body continuity requires re-authorizing the WhatsApp Business API channel in Zoho post-migration. We document this limitation explicitly during the data audit phase.

Planports Companies map to Zoho CRM Accounts. The Company domain and address fields migrate to Account Name, Website, and Address fields. Account is created before any Contact import in the migration sequence so that the Account-Contact lookup relationship is satisfied at the moment of Contact insert. Any Company-level custom fields (e.g., sector classification) map to custom Account fields.

Planports Deals are structured into custom pipeline stages per industry vertical such as health tourism referral stages or real estate viewing stages. We map each Planports pipeline to a Zoho CRM Potential with a corresponding Potential Name, Amount, Closing Date, and Stage. Zoho Potential Stage values are configured as a picklist in the destination schema to match the Planports stage names, with probability percentages mapped from Planports where available. Stage mapping is confirmed with the customer before production migration.

Planports Process boards use a Kanban layout to track sales and marketing workflows across custom stages. Zoho CRM has no direct Kanban equivalent for arbitrary custom processes, but we create a custom module in Zoho to replicate the Process board structure, mapping board columns to a Status picklist and card records to individual module entries. Any conditional automation rules attached to board columns are not migrated; we document each Process board and its automation triggers in the written inventory for the customer to rebuild in Zoho Blueprints or Deluge scripts post-migration.

Planports Quotes are linked to Deals and contain line items, pricing, and approval status. They map to Zoho CRM Quotes. Quote line items migrate as individual Quote Items with Product Name, Quantity, Unit Price, and Discount. Quote approval status migrates as a Zoho custom field or uses Zoho's built-in approval workflow which the customer configures post-migration.

Planports Orders track post-sale items, quantities, and status linked to a Contact and Deal. They map to Zoho CRM Sales Orders. The Contact and Deal lookups migrate as Customer Name and Deal Name references respectively. Financial settlement and accounting data may require coordination with Zoho Books if the customer uses that module; we flag this during scoping and include a Zoho Books integration as a separate engagement option.

Planports Activities log calls, emails, meetings, and manual notes against Contact or Deal records. We migrate Activity records to Zoho Tasks and Events preserving timestamps, owner attribution, and linked entity references. Call activities map to Zoho Tasks with Sub-Task type set to Call; email activities map to Tasks with activity type noted; meeting activities map to Zoho Events with Start Date Time, End Date Time, and Location preserved. The Zoho Data Migration wizard supports CSV import of Activities up to 5 GB per file.

Planports CRM uses industry-specific custom fields on Leads, Contacts, Deals, and Accounts particularly in health tourism (referral sources, treatment packages), real estate (property IDs, viewing schedules), and digital agencies (campaign IDs, ad spend). We audit every custom field during the pre-migration data review, produce a field mapping matrix, and pre-create matching custom fields in Zoho CRM before data load. Custom field types in Zoho (text, number, picklist, lookup, date, currency) are matched to the source field type. Note that custom fields are not available on the Zoho CRM free tier; the migration scope requires a Standard or higher Zoho plan.

Planports Owner records and deal assignment keys map to Zoho CRM Users. We resolve owners by email match during migration. Any Planports Owner without a matching Zoho User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Zoho User provisioning requires the customer to assign appropriate roles and profiles during the Zoho setup phase, which we coordinate before the production migration step.

Files uploaded to Planports Contact or Deal cards can be exported individually per record through the Planports interface. We migrate file attachments as Zoho CRM Attachments linked to the parent record. Bulk attachment migration requires the Planports API key add-on to be active; without it, we migrate attachments individually from the per-record export. We flag this during scoping and include the API key cost in the proposal if required.