Migrate from Civicrm to monday CRM

CiviCRM Individual contact subtypes map to Monday.com CRM People items. We extract first_name, last_name, email, phone, address fields (street, city, state_province, postal_code, country), and birth_date. The People item also captures job_title and company links via Monday.com's relationship column pointing to the mapped Company board item. Nickname and prefix (e.g., Dr., Hon.) migrate to a text column since Monday.com CRM People do not have native equivalent fields.

CiviCRM Household contacts have a household_name but no individual name. We map household_name to the People item Display Name and preserve all household member Relationships (household_member_of) as Monday.com relationship column links. The customer chooses during scoping whether to represent each Household as a separate People item with a custom Household type tag or as a named Group on the Contacts board.

CiviCRM Organization contacts map to Monday.com CRM Company items. organization_name becomes the Company Name field. Legal_name, sic_code, industry, and annual_revenue migrate to custom columns. Website and primary email map directly. Companies are imported before Individual contacts so that the company link on People items resolves correctly at insert time.

CiviCRM relationships (household_member, employee_of, spousal, etc.) connect two Contact records with a relationship_type. We map these to Monday.com CRM relationship columns on People items where the platform supports direct person-to-person linking, and to a custom link column (URL or text referencing the related record ID) where the specific relationship type is not natively supported. Bidirectional relationship types are preserved with links on both ends.

CiviCRM Activities (calls, emails, meetings, tasks) map to Monday.com CRM activity log entries on the relevant People or Deal item timeline. We preserve activity_type (call, email, meeting, task), subject, date, details, duration, and assignee. Activity records with no specific target contact or deal attach to the most recently modified related contact. Historical activities that represent pipeline-adjacent work (e.g., a meeting logged against a contact who is a donation prospect) attach to both the People item and the related Deal item if a deal exists in the target.

CiviCRM Contributions include financial_type, total_amount, currency, receive_date, payment_instrument, and source. Since Monday.com CRM has no native contributions or donations object, we create a custom Contributions board with columns for amount, currency, financial_type, payment_instrument, receive_date, and contact_name (linked via Monday.com relationship column to the relevant People item). Complex price-set line items are flattened to one contribution row per transaction. Note that payment gateway data and card numbers do not migrate per PCI compliance scope.

CiviCRM Membership records include type, status, start_date, end_date, source, and join_date. We map these to a custom Memberships board with membership_type, status, start_date, end_date, and a relationship column linking to the People item. Membership Price Sets introduce tiered structures (e.g., Annual Gold, Monthly Silver) that we represent as a status column or a dedicated membership_type text column. The customer chooses during scoping whether memberships are represented as a separate board or as custom columns on the People item.

CiviCRM Events with event_type, start_date, end_date, location, and participant_count map to a custom Events board in Monday.com CRM. Event status (scheduled, completed, cancelled) maps to a Status column. Participant roles and event fee information migrate as custom columns. Price set event fees are flattened to a single registration_fee amount per event row. Note that online registration profiles and participant-specific registration data do not have a Monday.com equivalent and require a separate registration form rebuild.

CiviCase stores case_id, case_type, status, start_date, subject, and a linked chain of activity records. Monday.com CRM has no native case management object. We create a custom Cases board with case_type, status, start_date, end_date, subject, and assignee columns, and link the case item to the related People item via a relationship column. Each CiviCase activity chain is preserved as separate activity log entries on the Cases board timeline. Case statuses are enumerated per case_type from the CiviCase XML entityType definitions and mapped to Monday.com Status column values during scoping.