Migrate from Perfectview to HighLevel

Perfectview's Relation object is a single entity that combines company fields and individual contact fields. We split each Relation into one GoHighLevel Account record (using the company name and address fields) and one Contact record (using the individual name, email, phone, and role fields). Where a Relation has multiple contacts (roles), we create one Contact per role and link all to the same Account. The original Relation ID is preserved in a custom field pv_relation_id__c on both the Account and Contact for audit trail and cross-reference.

Perfectview Activities are timestamped engagement records with type, subject, body, and owner. We map calls to GoHighLevel Tasks with TaskSubtype=Call, emails to Tasks with activity type set to Email, meetings to Events, and standalone notes to Notes. All parent lookups (Contact, Account, Opportunity) are resolved via the Relation split mapping before insert. Activity dates are preserved in ActivityDate fields to maintain the timeline ordering that sales teams rely on.

Perfectview Lead data may exist as a Relation lifecycle stage rather than a distinct object. We identify records where the Relation represents an unqualified prospect and import them as GoHighLevel Contacts without an Account link (orphaned Contacts), flagging them for the admin to attach to an Account or convert to a GoHighLevel Opportunity. Lead source, status, and score migrate as custom Contact fields.

Perfectview Cases with status, priority, assignee, and conversation history migrate to GoHighLevel. Depending on whether the customer's GoHighLevel instance has Service Cloud enabled, Cases land as Opportunities with a custom Case status pipeline or as Tasks with custom fields. The parent Relation is resolved to the Contact-Account pair during migration. Complex case-to-contact threading requires manual review if the case history spans multiple Relation roles.

Perfectview Quote line items migrate as Opportunity custom fields or as a structured data block in a custom GoHighLevel object. Quote total, status, validity date, and line item details (product, quantity, price) transfer with Opportunity-level lookups. Note that GoHighLevel's native Quote object is part of the Sales Cloud integration and requires a Salesforce connection; if the customer does not use Salesforce, we implement a Custom Object Quote equivalent.

Invoice records migrate to a GoHighLevel Custom Object named Invoice with fields for invoice number, date, amount, status, and line items. Invoice numbers may need renumbering in GoHighLevel to comply with the destination platform's sequential numbering rules. Payment status and outstanding balance transfer as custom fields. We do not migrate payment gateway links or financial reconciliation data that depends on Perfectview's billing module.

Perfectview documents migrate by extracting file metadata (name, type, size, upload date) and storing it as a GoHighLevel Contact or Account custom field with the file URL. Actual file bodies migrate via GoHighLevel's Media Library API. If the bulk export function is used as the primary data source (due to API rate limits), we fall back to UI-based document download and re-upload. Document-to-Relation links are preserved as custom field lookups on the migrated Contact or Account.

Perfectview User records and owner assignments on Relations, Activities, Cases, and Quotes migrate to GoHighLevel User records. We resolve owners by email match. Any Perfectview owner without a matching GoHighLevel User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Perfectview users migrate as inactive GoHighLevel users to preserve the owner history on historical records.