Migrate from Visual Practice to Freshsales

Visual Practice contacts map 1:1 to Freshsales Contacts when the record is associated with a company in Visual Practice. The contact's email, phone, job title, and address fields map directly. Owner assignment resolves by email match to a Freshsales user.

Visual Practice contacts without a primary company assignment route to Freshsales Leads. This handles practice records where the contact entity was used to track prospective clients before a company association was recorded. Leads can be converted to Contacts once an Account is assigned.

Visual Practice companies map directly to Freshsales Accounts. Company name, website, industry, employee count, and annual revenue map to their Account counterparts. Parent-company hierarchies in Visual Practice map to Freshsales Account hierarchy via the Parent Account field. Address and billing information are preserved as standard Freshsales Account fields during migration.

Visual Practice deals map directly to Freshsales Opportunities. The deal name, amount, expected close date, and owner all have direct counterparts. Deal stage maps to Opportunity Stage value-by-value per pipeline. Pipeline association in Visual Practice becomes the Freshsales Sales Pipeline assignment.

Visual Practice deal pipelines map to Freshsales Sales Pipelines. Each pipeline in Visual Practice becomes a named pipeline in Freshsales. Stage values are mapped one-by-one, and probability percentages and forecast categories are assigned per stage based on Freshsales conventions or your team's specifications.

Stage names and values from Visual Practice pipelines are mapped to Freshsales stage values. If Freshsales lacks a matching stage name, the closest equivalent is used and flagged for your review. Probability and forecast category are reapplied per Freshsales pipeline settings.

Visual Practice custom properties on contacts (beyond standard fields) migrate as Freshsales custom fields. These require creation in Freshsales before migration runs — field type (text, number, picklist) is inferred from the source data values. Notes on the transformation are documented per field.

Visual Practice deal-level custom properties (e.g., practice-specific billing codes, referral sources, service tiers) migrate as Freshsales Opportunity custom fields. Freshsales requires explicit field creation with type specification before data ingestion. We deliver the field creation spec as part of the pre-migration plan.

Visual Practice activity logs (calls, emails, notes) map to Freshsales Tasks. Task Subject, description, date, and owner are preserved. The activity type is encoded in the Task Type field (Call, Email) for filtering. Original timestamps are retained for reporting continuity.

Visual Practice meeting records map to Freshsales Events with start time, end time, title, and attendee information. Owner assignment resolves by email match. Events are linked to the parent Contact or Opportunity record where a linkable association exists in the source.

Visual Practice file attachments linked to contacts, companies, or deals are re-uploaded to Freshsales Files. Each file is associated with the target record (Contact, Account, or Opportunity) by ID after migration. File size limits apply per Freshsales storage tier. All original filenames and creation timestamps are retained to maintain document traceability.

Visual Practice owner records map to Freshsales users by email address match. Any Visual Practice owner without a matching Freshsales email is flagged before migration. Your team either creates a Freshsales user for each unmatched owner or assigns those records to a fallback user.

If Visual Practice stores products or service line items, these migrate as Freshsales Products with name, price, and description. Products are linked to Opportunities via the Opportunity Products junction in Freshsales, allowing deal line items to reflect the source pricing.

Visual Practice workflows and automations do not migrate. We export the workflow definitions in a machine-readable format so your Freshsales admin can reference them when building equivalent automations in Freshsales' workflow builder. This is a manual rebuild step handled outside the data migration.