Migrate from Crust CRM to monday CRM

Crust CRM Contact records map to Monday.com CRM Person records. Standard fields (name, email, phone, address) map directly. Lifecycle stage from Crust CRM migrates as a custom label field on the Person record. If Crust CRM uses a separate Lead object distinct from Contact, unqualified leads map to Person records with a lead_status custom column, while qualified leads map to Person records with a Contact label. The person-company linkage resolves via the Monday.com CRM person-to-company relationship after the Company import phase completes.

Crust CRM Company records map to Monday.com CRM Company records. Company name, domain, industry, employee count, and address fields migrate to their Monday.com CRM equivalents. We deduplicate on company domain name during import. Company records are imported before Person records so that the person-company relationship is established at insert time rather than patched afterward.

Crust CRM Deal records map to Items on the Monday.com CRM Deals Board. The deal amount, close date, and pipeline stage migrate to numeric, date, and status columns respectively. Crust CRM custom deal fields (discount codes, product interest, deal source) map to custom columns on the Item. The Deal-to-Company linkage is preserved by linking the Item to the corresponding Monday.com CRM Company record.

Crust CRM pipeline configurations (with named stages, stage order, and probability percentages) map to Monday.com CRM Status columns on the Deals Board. We collect the full pipeline-stage map during discovery, configure the Status column with all stage values before migration, and set stage probabilities as informational metadata on the board. If Crust CRM uses multiple deal pipelines, each pipeline becomes a separate Monday.com CRM Deals Board.

Crust CRM custom modules require schema review during scoping. Each custom module becomes a dedicated Monday.com Board with Column types mapped to the Crust field types (text, number, date, dropdown, checkbox, URL, phone). Lookup relationships between custom modules and standard objects (Contact, Company, Deal) map to Monday.com CRM's Board relation column or link-to-item column types. If the custom module has dependencies on other modules, we resolve parent-record existence before inserting child records.

Crust CRM engagement history (calls, emails, meetings, notes attached to Contact, Company, or Deal records) migrates as pulse update records on the corresponding Monday.com CRM Person or Item. Each engagement becomes a pulse note with the original timestamp, engagement type label, and content preserved. The pulse-based approach preserves the timeline against the correct Person or Item without requiring a separate activity object.

Crust CRM Task records attached to Contacts, Companies, or Deals migrate as Items on the Monday.com CRM Tasks Board or as sub-items on the parent Person or Deal Item. Task due date, status, priority, and assignment migrate to corresponding columns. Completed status maps to Done; open tasks map to the default working status on the board.

Crust CRM User records and owner assignments on Contact, Company, and Deal records resolve by email match against Monday.com CRM workspace members. Any Crust Owner without a matching Monday.com User goes to a reconciliation queue for the customer to provision. Owner assignments on imported records use Monday.com's person or member column type to link the record to the correct workspace user.

Crust CRM file attachments associated with Contact, Company, or Deal records are exported individually with their filename and parent record association preserved. We re-attach files in Monday.com CRM using the file upload API, linking each file to the corresponding Person or Item via the update or link column. If the attachment storage backend in Crust CRM is a local filesystem path, we coordinate with the customer's technical team to obtain file access before export.