Migrate from CRUMP CRM to monday CRM

CRUMP CRM Contacts from Dynamics 365 export as items on a monday.com Contact board. Each item carries typed columns for name, email address, phone number, company association (via link column to the Account item), owner assignment (via People column), and lifecycle stage. We use the Dynamics 365 contact fullname field to populate the item title and the emailaddress1 field for email column typing. If the source org uses Dynamics 365 duplicate detection rules, we apply the same matching logic during monday.com item creation to avoid duplicate contacts.

CRUMP CRM Accounts map to items on a monday.com Account board. Account is created before Contact import so that the relationship link column is satisfied at the moment of contact item creation. The Dynamics 365 accountid GUID is stored as a text column on the monday.com item for reconciliation purposes. Parent account hierarchy from Dynamics 365 maps to a subitem structure under the primary Account item in monday.com rather than a foreign-key lookup.

CRUMP CRM Deals (Dynamics 365 Opportunities) migrate to a monday.com Deal board. Pipeline stages from Dynamics 365 (for example, Prospecting, Qualification, Proposal, Negotiation, Closed Won, Closed Lost) map to Status column groups on the Deal board. Deal value, estimated close date, and probability are mapped to Number and Date columns. The link column on each Deal item points to the associated Account item, resolving the Opportunity-to-Account relationship at migration time.

CRUMP CRM Tickets (Dynamics 365 Cases) migrate to a monday.com Support or Helpdesk board. Case status (New, Active, On Hold, Resolved, Closed) maps to Status column groups. Priority, description, and linked contact are mapped to Priority, Text, and People columns respectively. Custom fields attached to tickets in Dynamics 365 are enumerated during audit and created as typed monday.com columns before ticket import begins.

CRUMP CRM Projects (Dynamics 365 Project Service Automation module) do not have a direct monday.com CRM equivalent. We create a Project board where each project is an item, and project-level milestones or phases become Groups within the board. Task-level detail from Dynamics 365 Projects is complex and may exceed monday.com's native task depth; we migrate the project record with status, dates, assigned team members, and budget but document task-level records for manual entry or a separate project-focused monday.com board if the customer requires it.

CRUMP CRM user accounts and their role assignments map to monday.com team member accounts. We extract every distinct owner referenced on Contact, Account, Deal, and Case records and provision monday.com team member invites for any user without an existing account. Inactive Dynamics 365 users are archived rather than imported to avoid ghost records. Role mappings (Salesperson, Sales Manager, Support Agent) are preserved as Text columns on relevant boards rather than a native role model.

CRUMP CRM invoicing records (Dynamics 365 Finance module) migrate to a monday.com Invoice board as items. Line items, totals, and payment status are mapped to Number and Status columns. The relationship between an invoice and its originating Deal or Project is reconstructed from the Dynamics 365 export by linking the invoice item to the corresponding Deal or Project item via a link column at migration time. This step requires the Deal or Project to exist in monday.com before the Invoice import phase.

CRUMP CRM custom Dynamics 365 entities are enumerated during the audit phase and each is assigned a dedicated monday.com board. The board's columns are configured to match the custom entity's attributes, with field types inferred from the Dynamics 365 attribute type (string to Text, integer to Numbers, date to Date, lookup to Link). Lookup relationships between custom entities are preserved as Link columns between the relevant monday.com items. This is the highest-risk part of the migration because no two Dynamics 365 deployments share the same custom entity set.

CRUMP CRM activities (Dynamics 365 activities: tasks, phone calls, emails, appointments, notes) are merged into a monday.com Activity board or stored as subitems under their parent Contact, Account, or Deal item. We distinguish activity type via a Status column group or Label column and preserve the original timestamp and owner. Email content migrates as a long-text column. We do not migrate email attachments as binary blobs through the monday.com API; attachments are documented separately for manual upload or SharePoint link restoration.