Migrate from HighQ to Freshsales

HighQ site members map to Freshsales agents. We resolve by email match — if a HighQ user email exists as a Freshsales agent, records assign to that agent. Unmatched users are flagged for your team to either create Freshsales accounts or assign to a fallback owner before migration runs.

HighQ iSheets with person-level columns (first name, last name, email, phone, job title, company) map directly to Freshsales Contacts. Standard Freshsales Contact fields are populated; any iSheet columns without a Freshsales equivalent become custom fields on the Contact object (custom fields available on all plans).

HighQ iSheets tracking prospect information with lead-status columns migrate to Freshsales Leads. The lead_status value maps to Freshsales Lead Status pick-list. Freshsales Lead fields like lead_source, lead_score, and lifecycle_stage are populated from corresponding iSheet columns if present; otherwise they default to the configured Freshsales defaults.

HighQ iSheets with organization-level columns (company name, industry, employee count, annual revenue, website) map to Freshsales Accounts. The account_name field maps directly; industry and number_of_employees use Freshsales pick-list and number fields respectively. Parent-company relationships in HighQ iSheets map to Freshsales Parent Account lookup if both organizations exist in the migration scope.

HighQ iSheets representing deal or pipeline data — with deal name, amount, stage, close date, owner — map to Freshsales Deals. The deal_name maps to Freshsales Deal Name; amount maps to Deal Amount (numeric); close_date maps to Expected Close Date. Pipeline stages from HighQ map to Freshsales Deal Stages (which are configurable per pipeline in Freshsales).

HighQ pipeline stages (e.g., Prospect, Qualified, Proposal Sent, Closed Won, Closed Lost) map value-by-value to Freshsales Deal Stage values. Freshsales supports multiple pipelines with different stage sets per pipeline — we configure the stage mapping per pipeline during schema setup and preserve stage-entry timestamps as custom datetime fields for reporting continuity.

HighQ iSheets containing product or service catalog data map to Freshsales Products. Fields like product_name, sku, unit_price, and product_description map to Freshsales Product Name, SKU, Unit Price, and Description. Products must be created before Deals can reference them via Deal Product entries.

HighQ Tasks (checklist items, action items assigned to users) migrate to Freshsales Tasks. Original due dates, assignees (resolved by email to Freshsales agents), and task status are preserved. HighQ subtasks are collapsed to a single task with the parent task name prefixed, as Freshsales Tasks do not support hierarchical nesting.

HighQ file attachments (documents uploaded to sites or linked in iSheet rows) are downloaded and re-uploaded to Freshsales as file attachments on the mapped record. We preserve the original file name, MIME type, and upload date. Freshsales file storage limits apply per plan (Growth: 2GB per user; Pro: 5GB per user; Enterprise: 100GB per user).

HighQ Workflows with automated rule chains, task assignments, and notification triggers do not migrate to Freshsales. The workflow logic must be rebuilt in Freshsales Workflows using Freshsales' own rule builder. We export the HighQ workflow definitions as a structured JSON document so your Freshsales admin can reference them during rebuild. This is disclosed upfront and included in the scope estimate.

HighQ iSheets with column types that have no Freshsales standard equivalent (e.g., complex lookup columns, formula columns, or multi-select pick-lists) require Freshsales custom fields or Enterprise-tier custom objects. We analyze the iSheet column schema before migration and deliver a custom field creation plan for Freshsales. Enterprise plan is required for custom objects; Growth and Pro plans support custom fields on standard objects.

HighQ role-based permissions per site have no direct Freshsales equivalent. Freshsales uses profile-based and field-level permissions on standard CRM objects. We recommend your Freshsales admin review the Freshsales permission model post-migration and assign profiles based on the user's function. This is a post-migration configuration step, not a data migration item.