Migrate from Perfectview to Zoho CRM

Perfectview's Relation object conflates company and individual contact data into a single entity type. We split each Relation into one Zoho Account record (using the Relation's company name and address fields) and one or more Contact records (extracting the individual name, email, phone, and role fields from within the Relation). The original Relation identifier is preserved in a custom field pv_relation_id__c on both the Account and Contact for audit traceability. The split logic is validated against a sample of 100 live records before bulk migration to ensure no duplicates or orphaned Contact records are created. If a Relation contains no individual contact details, it becomes an Account-only record.

Perfectview Activities (calls, emails, meetings, tasks) are well-structured and timestamped. Calls and tasks migrate as Zoho Task records with the Task Type set to Call for call engagements. Meetings migrate as Zoho Event records with Start DateTime, End DateTime, and Location preserved. Emails migrate as Task records with the email body in the Description field and Subject preserved. We resolve the parent record lookup (AccountId or ContactId) from the linked Relation identifier during the transform phase and attach Activity records to the correct Zoho Account or Contact.

Perfectview Lead records migrate directly to Zoho Leads. Lead status values map to Zoho's Lead Status picklist. Lead source and any scoring data from Perfectview migrate to custom fields in Zoho's Leads module. If the Perfectview lead is already linked to a Relation, we either convert the Lead pre-migration in Perfectview (to create the Contact-Account linkage) or maintain it as a Zoho Lead and allow the customer's admin to convert manually post-migration.

Perfectview complaint management and support ticketing records migrate to Zoho Cases. Case status, priority, assignee, and conversation history (stored as Activities linked to the Case) migrate intact. The original Relation link is resolved to the newly created Zoho Account or Contact during import. If the destination Zoho org does not include a Service module license, Cases migrate as Tasks in a dedicated Case queue with a custom Status picklist.

Perfectview Sales module Quote records migrate to Zoho Quotes with line items, pricing, and Quote status preserved. Quote-to-Relation links are resolved to the newly created Zoho Account or Contact. Zoho Quotes require a Price Book to be associated before the Quote can be generated; we create the necessary Price Books during schema setup if the customer has active product pricing in Perfectview. Quote PDFs are not importable via the Data Migration wizard and are flagged as a manual handoff item.

Perfectview invoice records migrate with line items and payment status. Invoice numbers may need renumbering in Zoho if they conflict with existing Zoho invoice sequences; we flag this during scoping and apply an offset prefix if required. Outstanding balance and payment history migrate as custom fields or as linked Invoice Line Items in Zoho's Invoices module. Note that Zoho Invoices is part of the Zoho Books integration in some editions; if the customer does not have Zoho Books, Invoice records migrate as Quotes with a custom invoice flag.

Perfectview document storage files migrate as Zoho Attachments linked to the parent Account, Contact, Case, or Quote record. We retrieve documents via API where enabled in Perfectview, falling back to the UI export for bulk downloads. Document metadata (filename, upload date, author) migrates as a Zoho Note record referencing the attachment. Large document sets (over 5,000 files) require chunked export passes to stay within Zoho's attachment import limits.

Perfectview custom fields on Relations and other objects are discovered during the discovery phase and mapped to equivalent Zoho CRM custom fields. Zoho creates custom fields during the Data Migration wizard if the import file contains column headers that do not match existing Zoho field names. We verify field type compatibility (text vs. picklist vs. date) during the mapping phase and apply Zoho's field type constraints: custom fields are not available in the Free edition, and Lookup and Formula fields are restricted to paid editions above Standard. If a Perfectview custom field uses a data type not supported by Zoho, we flag it and propose the closest equivalent.

Perfectview User records and owner assignments on Relations, Activities, Cases, and Quotes migrate directly to Zoho Users. We resolve owners by email match. Any Perfectview Owner without a matching Zoho User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Active/inactive status is preserved from Perfectview. Owner-to-record links are reassigned to matching Zoho Users with a manual review step for any mismatches.

Perfectview workflow rules, trigger conditions, and automated sequences are not exposed through any export mechanism. We document all active workflows during the discovery call, capturing trigger conditions, action types, delays, and notification settings. This documentation is delivered as a written inventory with a recommended Zoho Blueprint or Workflow equivalent for each item. The customer's admin rebuilds them in Zoho's visual workflow builder post-migration. For teams with complex automation chains, this rebuild work adds 2-5 hours per significant workflow and should be scoped separately from the data migration.