Migrate from Glaze CRM to Nutshell

Glaze CRM Company records map directly to Nutshell Account records. The company name, address fields, industry classification, and any standard company properties transfer 1:1. Nutshell Accounts serve as the parent entity for People records, so we import Accounts first and validate the count before beginning People migration. If Glaze CRM exposes a company domain field, we map it to Nutshell Account website. White-label Glaze CRM instances may use non-standard company field names; we infer types from the customer's sample export during scoping before building the field mapping spreadsheet.

Glaze CRM Contact records map to Nutshell People. We resolve the Account (Company) lookup by matching the Glaze CRM company_id or company name against the Nutshell Account created in the first import phase. Name, email, phone, title, and address fields transfer directly where present. Custom contact properties from Glaze CRM require a custom field to be pre-created in Nutshell before migration; we document required custom field names and types during schema audit. Completed vs. open contact status flags map to Nutshell's person active/inactive classification.

Glaze CRM Deal records map to Nutshell Deal records. Deal name, amount, expected close date, and owner assignment transfer 1:1. Pipeline stage names from Glaze CRM map to Nutshell Deal status values; we document the existing Glaze CRM pipeline stages during discovery so the customer can configure matching Nutshell Deal stages before migration or accept our recommended stage-name mapping. Deal-to-Account and Deal-to-Person lookups resolve via the account_id and contact_id fields after the Account and Person imports complete.

Glaze CRM Lead records map to Nutshell Lead records where the destination Nutshell instance has the Lead module enabled. Lead source, status, owner assignment, and any standard lead properties transfer directly. If the customer uses Glaze CRM's lead scoring or rating fields, these migrate to equivalent Nutshell custom fields we pre-create during schema setup. Leads without a matching Account or Person link do not require parent-record resolution; Nutshell Lead accepts standalone records.

Glaze CRM Task records map to Nutshell Task records. Subject, due date, assignee (resolved via owner email to Nutshell User), status (open vs. completed), and linked entity (Contact, Company, or Deal) transfer with the lookup remapped to the Nutshell entity ID after parent imports. We preserve completed vs. open task flags, and set the Nutshell task due date from the Glaze CRM due date timestamp. Task notes and descriptions migrate as the task description body.

Glaze CRM User records map to Nutshell User accounts by email address match. We extract every distinct owner email referenced across Contact, Company, Deal, and Task records during discovery and reconcile against the target Nutshell instance's User list. Any Glaze CRM owner without a matching Nutshell User goes to a reconciliation queue; the customer's Nutshell admin provisions the missing User before record migration continues. Inactive Glaze CRM users with no associated records are excluded from the migration entirely.

Glaze CRM tags stored as string arrays per record migrate to Nutshell Tag records linked via the taggable API. Tags used for lead segmentation, contact categorization, and deal classification transfer as flat string values and are reapplied to the corresponding Nutshell records post-import. Multi-value tag fields from Glaze CRM split into individual Nutshell Tag assignments per record.

Glaze CRM custom fields on Contacts, Companies, and Deals require pre-creation in Nutshell before migration begins. We request a full Glaze CRM field inventory from the customer (exported from the instance settings) during scoping, infer field types from sample data values, and submit a Nutshell custom field creation checklist before migration day. Nutshell custom fields on People, Companies, and Leads support text, number, date, dropdown, checkbox, and currency types. Note: Nutshell does not support searching or filtering by custom field values post-import; this limitation is documented in the migration handoff for the customer's awareness.

Glaze CRM pipeline stages are organizational-level configuration that the customer replicates in Nutshell Deal settings before migration. We document the existing Glaze CRM pipeline names and stage values during discovery and provide a written mapping spreadsheet that the customer uses to configure matching Nutshell Deal stages. Each Glaze CRM pipeline maps to a separate set of Nutshell Deal status values; multi-pipeline Glaze CRM instances require the customer to configure corresponding pipeline scoping in Nutshell if they use multiple deal tracking tracks.

Glaze CRM document attachments per record store file metadata (filename, upload date, linked record reference) but the platform does not expose a documented file export API. We migrate document metadata as a linked record noting the filename, upload timestamp, and the source record it was attached to in Glaze CRM. Actual file binaries (PDFs, images, uploaded documents) require a separate file-transfer step coordinated with the customer outside the API migration scope; we provide a file-transfer checklist identifying each document and its source record for manual or semi-automated transfer.