Migrate from Perfectview to Freshsales

Perfectview Relations combine company and individual contact data into a single record type. We split each Relation into one Freshsales Account (using company-name, address, industry, and website fields) and one or more Freshsales Contacts (using the role, first name, last name, email, phone, and direct-address fields from within the Relation). Relations that represent a sole trader or individual without a separate company generate a Contact-only record with no parent Account. The split logic is validated against a live sample of 50+ Relations before bulk migration to confirm field extraction accuracy and flag any edge cases such as multi-role contacts or missing company data.

Perfectview Activities (calls, emails, meetings, tasks) attach to Relations. We map each activity type to the equivalent Freshsales object: calls become Task with TaskSubtype=Call, meetings become Event, emails become Email records, and standalone tasks become Task. Activity timestamps are preserved as ActivityDate. Owner resolution is by email match against the User table. Freshsales standard import limits to 25,000 records; for histories exceeding this, we use the Freshsales API with pagination and chunking rather than the CSV import path.

Perfectview Lead records (if used as a distinct lifecycle stage rather than a Relation status) map directly to Freshsales Lead. Lead status, source, and score custom fields transfer to Freshsales Lead fields or custom Lead fields. The customer chooses during scoping whether to treat all Relations with an 'incoming' status as Leads and qualify them post-migration, or to import them as Contacts on a specific Account.

Perfectview Cases (support tickets) map to Freshsales Cases with Case Status, Priority, and assignee preserved. Conversation history attached to the Case in Perfectview migrates as Email records linked to the Case. Relation-to-Case links are resolved during migration so the parent Account or Contact is attached to the Case via the WhatId.

Perfectview Quotes migrate as Freshsales Deals with line items mapped to associated Product records. The Quote header (quote number, validity dates, terms) becomes Deal custom fields since Freshsales Deals do not have a native Quote sub-object in the same structure. The customer defines whether to create a separate Quote object in Freshsales or to hold all pricing data within the Deal record.

Perfectview Invoice records (payment status, line items, amounts) migrate as Freshsales Deal records with custom invoice fields rather than a native billing object. Invoice number may require a prefix or renumbering to avoid conflicts with existing Freshsales Deal IDs. For teams requiring full invoice history, we create a separate custom object for Invoice records linked to the parent Account.

Perfectview Documents are retrieved via API where enabled, falling back to the UI export for bulk downloads. Document metadata (filename, upload date, owner, related Relation) migrates as Freshsales Notes attached to the parent Account or Contact via ContentDocumentLink. Binary file content migrates as Attachments where the destination account has storage capacity. We flag any documents exceeding Freshsales' file size limits for manual handling.

Custom fields on Perfectview Relations and other objects are discovered during the scoping phase and recreated in Freshsales with matching data types (text, number, date, picklist, checkbox, currency). Field-level mapping is documented in the field map deliverable. Freshsales Growth tier and above supports custom fields via Admin Settings; the destination account must be on a plan that supports the field count required. Multi-select picklist values from Perfectview map to Freshsales multi-select picklists.

Perfectview Users and Owner assignments on Relations, Deals, Cases, and Activities map to Freshsales Users by email address. We resolve all owner references during migration and flag any Perfectview Owner without a matching Freshsales User in a reconciliation queue for the customer's admin to provision before record import completes. Inactive Perfectview users are mapped to inactive Freshsales Users with their record history preserved.