Migrate from Perfectview to HubSpot

Direct map. PerfectView contacts migrate as HubSpot contacts with standard field translation (name, email, phone, job title). PerfectView stores relationship type as a per-contact field — this maps to a HubSpot custom contact property (relationship_type__c) rather than a native HubSpot construct.

Direct map. PerfectView company records map to HubSpot companies with standard field translation (name, domain, address, industry). HubSpot companies use a flat hierarchy model — parent-child relationships from PerfectView map to the Parent Company field in HubSpot. Multi-value pick-list properties from PerfectView require special handling to preserve all selected values.

PerfectView's relationship type classification (Decision Maker, Influencer, Vendor, Referrer, etc.) is stored as a per-contact property. This has no direct HubSpot equivalent — we create a custom pick-list property (relationship_type__c) and map each value. The property is available for HubSpot workflows and filtering after migration.

PerfectView deals map to HubSpot deals. The PerfectView sales funnel name becomes the HubSpot pipeline name. Each PerfectView stage (Suspect, Prospect, Qualified, Proposal, Negotiation, Closed Won/Lost) maps to a HubSpot deal stage value — value-by-value mapping is required because stage names differ by installation.

PerfectView activities map to HubSpot engagements. Calls become HubSpot call engagements with original timestamps and owner preserved. Emails become email engagements with subject and body intact. Meetings become meeting engagements with start/end times and location data where available.

PerfectView notes migrate as HubSpot engagement notes. The note body, create date, and owner are preserved during migration. Notes attached to contacts or companies link to the corresponding HubSpot record by email or company domain match for immediate association.

PerfectView documents attached to contacts, companies, or deals are downloaded and re-uploaded as HubSpot Files. The original filename is preserved for traceability and audit purposes. Large file handling follows HubSpot's file size limits per attachment during the upload process.

PerfectView leads map to HubSpot contacts with a default lifecycle stage of 'lead'. PerfectView does not have a lifecycle stage property, so we assign a default stage during migration — teams that use PerfectView's lead/contact distinction should specify the mapping rule before migration runs.

PerfectView custom properties at the contact level require creation of equivalent HubSpot custom properties before import. We audit all custom properties during the planning phase, create them in HubSpot with matching types (text, number, date, pick-list), and map them during import.

PerfectView custom properties at the company level map to HubSpot company properties using a creation-first approach. Custom properties must exist in HubSpot before the import batch runs. Multi-value pick-lists from PerfectView require special handling to convert all selections into a compatible format.

PerfectView marketing campaigns map to HubSpot campaigns with direct field translation. Campaign members (contacts associated with a campaign in PerfectView) migrate as HubSpot campaign members. Campaign type, status, and start/end dates are preserved as campaign properties during the migration.

PerfectView support tickets map to HubSpot tickets with status, priority, subject, and description preserved. PerfectView ticket categories map to HubSpot ticket pipelines — value mapping is required if status names differ between the two systems. The original ticket ID is stored in a custom field for traceability.