Migrate from Glaze CRM to monday CRM

Glaze CRM Contacts migrate to Monday.com CRM People Items. We map name, email, phone, and company association fields to the corresponding People column types. Company association becomes a link or connect board column pointing to the Company Item. Any Glaze CRM custom properties on Contact require a type-inference pass from a sample record export before we can assign the correct Monday.com column type (text, number, date, dropdown, multi-select, or checkbox). Multi-select fields become either Monday.com Tags or multi-select columns depending on the customer's preference.

Glaze CRM Companies migrate to Monday.com CRM Company Items on the same People board. We import Companies first so that the Company-Contact relationship can be established via the Monday.com connect boards column during Contact import. Address data, industry tags, and custom fields on Company follow the same type-inference process as Contacts. Company names serve as the deduplication key to prevent duplicate Company Items during import.

Glaze CRM Deals migrate to Monday.com CRM Opportunity Items. The deal name, amount, stage, and associated company or contact map to the corresponding Opportunity column types. We resolve the company lookup by matching the Glaze CRM company name to the Monday.com Company Item created in the prior phase, and the contact lookup by email address match to the People Item. Pipeline stages from Glaze CRM become Status column values on the Opportunity board.

Glaze CRM Leads migrate as separate Items if the customer requires a distinction between unqualified prospects and qualified contacts in Monday.com CRM. If the customer's Glaze CRM workflow treats Leads and Contacts as the same entity type, we migrate all records as People Items and add a custom Status or Label column to indicate lead source. The customer decides during scoping whether a separate Lead Item type is needed.

Each Glaze CRM pipeline becomes a separate Monday.com board. Pipeline stages become Status column values on the board, ordered to match the original Glaze CRM stage sequence. If Deals live on a pipeline in Glaze CRM, they import into the corresponding Monday.com board on the Deals group or a dedicated Opportunities group. We document the stage probability values (if any exist in Glaze CRM) as a Number column for reference even though Monday.com does not natively use stage probabilities the same way as Salesforce or HubSpot.

Glaze CRM Tasks migrate to Monday.com Items with a Task-type column or as subitems on the related Contact, Company, or Deal Item. We map subject, due date, assignee, status (open/completed), and linked entity. Assignee resolution uses email address matching to Monday.com team members. Completed vs. open task flags map to a Status column. Task associations to Contacts, Deals, or Companies are preserved by placing the Task Item in the correct group or linking via a connect boards column.

Glaze CRM custom fields on Contacts, Companies, and Deals do not have a documented type schema, so we request a full sample export showing all populated custom field values before migration. From this sample we infer field types: text values become text columns, numeric values become number columns, date strings become date columns, and comma-separated multi-values become multi-select columns. We build the Monday.com column schema in a staging board first, validate types with the customer, then deploy to production boards before data import begins.

Glaze CRM Users referenced as deal owners or task assignees are mapped by email address to Monday.com team members. We require the customer to provide a list of active Monday.com team members before migration, and any Glaze CRM owner without a match goes to a reconciliation queue for the customer to resolve. Inactive Glaze CRM users with no history in the migration scope are archived without transfer.

Glaze CRM tags migrate as flat string values and are reapplied in Monday.com CRM either as native Tags on Items or as multi-select column values depending on the customer's reporting needs. Tags used for segmentation map to multi-select columns so they can be filtered in board views; tags used for informal labeling map to Monday.com Tags.