Migrate from Glaze CRM to Freshsales

Glaze CRM Contact records map directly to Freshsales Contact. Email address serves as the dedupe key. We map standard fields (name, email, phone, address, company association) and any Glaze CRM custom contact properties to Freshsales custom contact fields. Multi-select custom fields require type inference from sample data or customer confirmation since Glaze CRM does not publish field type documentation publicly.

Glaze CRM Company records map to Freshsales Account. Company name serves as the primary dedupe key. We import Accounts before Contacts so that AccountId is available at Contact insert time to satisfy the lookup relationship. Address data, industry tags, and company-level custom fields map to equivalent Freshsales Account fields or custom fields.

Glaze CRM Deal records map to Freshsales Deal. Deal name, amount, stage, and associated company or contact transfer directly. Pipeline stages are configured per-organization in Glaze CRM, so we must reconcile stage names between the source instance and Freshsales deal stages. We document the existing Glaze CRM pipeline stages from the export and replicate them as Freshsales deal stages before migration.

Glaze CRM Lead records map to Freshsales Lead. Lead source, status, and owner assignment transfer directly. We preserve lead score and any custom lead fields in Freshsales custom fields. The customer decides during scoping whether to convert migrated Leads to Contacts and Accounts in Freshsales using Freshsales lead conversion rules, or to keep them as Leads for manual conversion later.

Glaze CRM pipeline stages map to Freshsales deal stages. We configure Freshsales deal stages to match the original stage names and probability percentages. If Glaze CRM has multiple pipelines, we document them as additional Freshsales pipelines if the destination plan supports multiple pipelines — Growth is limited to one pipeline; Pro and Enterprise support multiple.

Task records in Glaze CRM map to Freshsales Tasks. Subject, due date, assignee (resolved via User email mapping), status, and linked entity transfer directly. Task associations to Contacts, Deals, or Companies are remapped using the Freshsales entity ID resolved during migration. Completed versus open task flags are preserved.

Glaze CRM custom fields on Contacts, Companies, and Deals map to Freshsales custom fields of equivalent type. We request a full field inventory from the customer before migration and build the Freshsales custom field schema in a Sandbox org first. Multi-select fields in Glaze CRM require special handling — they often need to be split into separate Freshsales multi-select or text fields depending on the destination field type.

Glaze CRM User records representing team members map to Freshsales Users by email address. We resolve owners on Contacts, Deals, and Tasks by matching owner email to the Freshsales User table. The customer provisions Freshsales users matching the Glaze CRM user list before migration begins. Inactive users can be archived in Freshsales if they have no open records.