Migrate from Upvise to Freshsales

Upvise contacts without a lifecycle flag land as Freshsales Contacts. If Upvise records carry a lead/customer status flag, those with 'lead' designation split to Freshsales Lead. Contacts already identified as customers route to Freshsales Contact — the split is controlled by your Upvise contact status field value. Primary company association maps to AccountId; any additional company links surface as Account Contact Relationships.

Upvise companies map 1:1 to Freshsales Accounts. Company name maps to Account Name; domain to Website; industry pick-list maps value-by-value to Freshsales Industry field. Address fields (street, city, state, postal_code, country) map to Freshsales Billing Address compound field. Parent-company hierarchies in Upvise map to Account.Parent_Account_Id__c lookup where supported.

Upvise Jobs split by billable status. Billable Jobs with a monetary value map to Freshsales Opportunities (Name, Amount, Stage, Close Date, Owner). Non-billable Jobs or Project-style items map to Freshsales Tasks with the job name as Subject and the description as Task Description. This split requires a pre-migration rule definition from your Upvise job configuration.

Upvise job status values (e.g. New, In Progress, Completed, Lost) map to Freshsales Opportunity StageName pick-list values per pipeline. If you use multiple Freshsales pipelines, stage mapping is pipeline-specific. Probability values and forecast category are applied per Freshsales pipeline configuration.

Upvise allows a contact to be associated with multiple companies natively (N:N model). Freshsales contacts have a single primary AccountId. We migrate the most-recently-modified company link as primary, and any additional associations as Freshsales Account Contact Relationships — preserving the full association history.

Upvise custom fields created on Jobs via Options > Custom Fields are read from the Upvise schema and recreated as Freshsales custom fields on the Opportunity object. Field type is preserved (text, number, date, pick-list) and a custom pick-list field is created where the Upvise field uses a defined set of values.

Upvise contact-level custom fields migrate as Freshsales custom fields on both Contact and Lead objects for field continuity. If a pick-list field in Upvise uses a restricted value set, the Freshsales equivalent is created as a pick-list with the same allowed values to avoid data validation errors.

Upvise form submissions are structured records tied to contacts. In Freshsales, form submissions without a standard CRM equivalent are preserved as Notes with the form identifier and submission data in the Note Body. On Enterprise plans these can alternatively map to Custom Modules if your Freshsales admin pre-creates the module structure.

Upvise file attachments associated with Jobs or Contacts are downloaded and re-uploaded to Freshsales as Note attachments. File size limits on Freshsales apply (25MB per file for standard attachments). Inline images in Upvise notes are extracted, downloaded, and re-hosted as note attachments in Freshsales.

Upvise users are resolved by email match against Freshsales user accounts. Any Upvise owner without a matching Freshsales user email is flagged before migration and assigned to a fallback owner you designate. The fallback owner rule is defined in the pre-migration planning call.

Upvise's internal record ID for Jobs is stored in a custom text field (Source_System_ID__c) on the Freshsales Opportunity for traceability and delta-run de-duplication. This prevents records from being re-inserted on re-migration runs. The field also serves as an audit trail, enabling you to reference the original Upvise job identifier in Freshsales reports and dashboards, and it supports matching during subsequent data refreshes to update existing opportunities without creating duplicates.