Migrate from Glaze CRM to Salesforce Sales Cloud

Glaze CRM uses a single Contact object that may combine records that Salesforce treats as separate Lead and Contact objects. We define the split rule during scoping based on the customer's use of lead source, lead status, and lifecycle indicators within Glaze. Unqualified prospects with no associated Company map to Salesforce Lead; qualified contacts with a Company association map to Salesforce Contact attached to an Account. We preserve the original Glaze CRM record ID and any contact-level custom fields in custom Salesforce fields for reconciliation after migration.

Glaze CRM Company records map directly to Salesforce Account. The company name, address fields, industry tags, and any custom fields migrate as typed Salesforce fields. Account is imported before any Contact or Deal records so that the AccountId foreign key is satisfied at insert time. We use the Company record ID as the dedupe key if Glaze instances contain duplicate company names.

Glaze CRM exposes a separate Lead object in addition to Contact in some configurations. Lead records map to Salesforce Lead with standard field mappings: lead source, status, owner assignment, and any custom fields carry across. We apply the customer's Salesforce Lead Status picklist values during import, mapping from whatever status labels Glaze CRM uses.

Glaze CRM Deal records map to Salesforce Opportunity. Deal name, amount, expected close date, stage name, associated Company, and associated Contact migrate to the corresponding Salesforce Opportunity fields. Stage probability percentages from Glaze CRM are mapped to Salesforce StageProbability values during import.

Glaze CRM pipelines and their configurable stages map to Salesforce Record Types and Sales Processes on the Opportunity object. Each Glaze pipeline becomes a Salesforce Record Type, and the pipeline's stage sequence becomes a Salesforce Sales Process whitelisting only the relevant stage values. Stage probability percentages from Glaze migrate to Salesforce StageProbability.

Glaze CRM Task records map to Salesforce Task with subject, due date, assignee, status, and linked entity (Contact, Deal, or Company) preserved. We resolve Glaze CRM task associations to Salesforce records using the foreign key mapping established during the Accounts, Contacts, and Opportunities import phase. Completed versus open task flags migrate as-is.

Glaze CRM User records representing team members assigned as deal owners or task assignees map to Salesforce User records by email address. We run an email-match reconciliation against the destination Salesforce org's User table before production migration. Any Glaze CRM User without a matching Salesforce User enters a manual provisioning queue, and the customer's Salesforce admin provisions the User before record import resumes.

Glaze CRM tag strings migrate as flat string arrays applied to Salesforce records. We map tags to a Salesforce custom multi-select picklist field if one exists, or to a custom text field with semicolon delimiters. The customer chooses the tagging strategy during scoping based on how tags are used for segmentation in their Salesforce destination.

Glaze CRM Document attachments per record have no export API, so actual file binaries (PDFs, images, uploaded documents) cannot be migrated programmatically. We extract document metadata (filename, upload date, record association) and recreate ContentDocumentLink records in Salesforce linking to a placeholder filename. The customer's admin must re-upload actual files post-migration or use a separate file migration tool.

Glaze CRM custom fields on Contacts, Companies, and Deals require manual type inference from sample records because no public field type documentation exists. We request a representative Glaze CRM export covering all record types with custom fields visible, infer data types (text, number, date, picklist, multi-select), and pre-create Salesforce custom fields with the matching field type before data migration begins. Any fields that cannot be typed from the sample export are flagged for manual review.

Glaze CRM engagement history (calls, emails, meetings, notes) migrates to Salesforce Task (TaskSubtype=Call for calls), Event (for meetings), and EmailMessage (for emails) linked via WhoId to the migrated Lead or Contact and WhatId to the related Account or Opportunity. We use the Salesforce Bulk API 2.0 with batch chunking, exponential backoff, and parent-record lookup resolution because engagement history volumes typically exceed CSV loader capacity for mid-market accounts.

Glaze CRM supports custom object creation in some configurations. These map to Salesforce custom objects with __c API names. We pre-create the destination schema in Salesforce (custom object, fields, lookup relationships, validation rules) before any data import. Custom object import runs last in dependency order because custom object records frequently have lookups to standard objects that must already exist.