Migrate from Rubi CRM to monday CRM

Rubi CRM Contact records map to Items in the Monday.com People board. Standard fields (name, email, phone, address) migrate as Monday.com text, email, phone, and location column types. We preserve any Rubi CRM custom contact properties as custom columns in the destination board. Contact-Company relationships are resolved by name lookup: where a Rubi CRM Contact has a linked Company record, we link the Monday.com Item to the corresponding Company board Item via the Connect Boards column.

Rubi CRM Company records map to Items in the Monday.com Companies board. Company name becomes the Item name; address, domain, and industry fields map to Monday.com text and location columns. Companies are migrated before Contacts so that the Connect Boards relationship is satisfied at Contact insert time. Where no Rubi CRM Company is linked to a Contact, we create a standalone Company Item and link it.

Rubi CRM Member records are a distinct type tied to the membership module and carry a Member ID and membership status. We map Member ID to a Monday.com text column and membership status to a Status column. Rubi CRM membership tier names (Gold, Silver, Bronze, Standard, or custom tiers) require field-value mapping during scoping because they are not enumerated picklists in Rubi CRM; we extract the distinct values from the export and create matching Monday.com Status options before migration.

Rubi CRM Membership records track individual subscriptions against Member profiles with start dates, end dates, and tier names. We map these as Items in a dedicated Memberships board, with a Connect Boards column linking each Membership Item to the corresponding Member Item in the Members board. Start date and end date migrate as Monday.com Date columns; tier name migrates as a Status or text column. Rubi CRM does not export full subscription history in a single pass, so we flag any multi-year or lapsed-reinstatement records that require a separate export run during the scoping call.

Rubi CRM Events are objects with bookings tied to Contacts or Members. We map event name and event date to Monday.com Item name and Date column, and booking status (Registered, Attended, Cancelled, Waitlisted) to a Status column. Seat-level attendance data requires a separate export run from the Events module because it is stored as a sub-record. We link each Event Item to the originating Contact or Member Item via the Connect Boards column using name-matching where no foreign key is present in the Rubi CRM export.

Rubi CRM Tasks map to Items in a Tasks board with owner, due date, and status preserved. Owner assignment resolves via email lookup against the Monday.com workspace User list. Due date maps to a Monday.com Date column; status (Not Started, In Progress, Complete) maps to a Status column. Tasks with a linked Rubi CRM Contact or Member carry a Connect Boards link to the corresponding Item in the People or Members board.

Rubi CRM uses a Kanban-style pipeline view with user-defined stage names stored as custom fields against deal records, not a native pipeline object. We extract the distinct stage values during the scoping call, create the equivalent Monday.com CRM Sales board with matching stage groups in the pipeline view, and deliver a written board-design specification mapping each Rubi CRM stage name to a Monday.com Status group. The deal records themselves are migrated as Items with value, close date, and contact link columns, assigned to the appropriate stage group.

Rubi CRM allows custom fields per record type but does not expose a schema endpoint. We discover custom field names during the export scoping phase by extracting field labels from the export header row. We then create matching custom columns in Monday.com (text, number, date, status, or dropdown) before migration. Custom field types are inferred from the data values; any ambiguous type (e.g., free-text that might be a picklist) is flagged for the customer to confirm during scoping.