Migrate from Rubi CRM to Nutshell

Rubi CRM Contacts map directly to Nutshell Contacts. Standard fields (name, email, phone, address) migrate 1:1. Any Rubi CRM custom contact properties are discovered during the scoping phase and created as matching Nutshell custom fields before import. The Contact is the parent record for most other object types, so it migrates first.

Rubi CRM Company records map to Nutshell Companies. The Company-Contact relationship is preserved by establishing the Nutshell Company first and resolving the CompanyId on the Contact record at import time. Name-matching handles cases where no explicit foreign key is present in the Rubi CRM export.

Rubi CRM's Member record is a distinct type tied to the membership module and stores member ID, tier name, and status. Nutshell has no native Member object, so we map Member ID to a custom text field member_id__c and membership status to a custom picklist field membership_status__c. Tier names require a value-mapping table during scoping because Rubi CRM tier names are user-defined and must align with Nutshell picklist values.

Individual Membership records (subscription against a Member profile) map to the Contact with custom fields for start_date__c, end_date__c, and membership_tier__c. Rubi CRM does not export full subscription history in a single pass, so we run a separate export query against the Membership module if historical renewal records are required; otherwise we migrate the current active membership only.

Rubi CRM Events map to Nutshell Events with event name, date, and booking status preserved. Seat-level attendance data requires a separate export run from the Events module. We map booking status to a custom picklist field event_booking_status__c on the Nutshell Event. Event records are linked to their originating Contact via the event_registrant__c relationship.

Training bookings are a Rubi CRM object type with sessions tied to Contacts or Members. We map the training course name, session date, and booking status to Nutshell Event records using a custom field training_course__c and event_type = 'Training' to distinguish from standard events. Completion status migrates to a custom picklist attendance_status__c.

Rubi CRM uses a Kanban-style pipeline view where stage names are user-defined custom fields stored against deal records, not a native pipeline object. We extract the distinct stage values during scoping, create matching Deal stage values in Nutshell's pipeline configuration, and map the Rubi CRM stage custom field to Nutshell Deal.stage during import. This configuration is performed before any deal data is loaded.

Rubi CRM Deals map to Nutshell Deals. Deal name, amount, and expected close date migrate directly. The Kanban stage custom field resolves to the Nutshell Deal stage configured in the previous step. Owner assignment resolves by email match to Nutshell User records.

Email interactions logged via Rubi CRM's Outlook plugin are stored as Activities linked to Contacts. We export activity timestamps, subject, and body text. Email body migrates to a Nutshell Activity record with body preserved as text. Thread-level email threading from the original message is not preserved because Rubi CRM does not export thread ID. Call and meeting activities from the Outlook plugin migrate as Task (subtype call/meeting) or Event records in Nutshell.

Rubi CRM Tasks (owner, due date, status, description) map directly to Nutshell Tasks. Owner assignment resolves by email match. Due date and status migrate with type preservation. Open and completed task status maps to Nutshell's open and completed status values.

Rubi CRM allows custom fields per record type but does not expose a schema endpoint. We discover custom field names, types, and values during the export scoping phase. Nutshell custom fields are created in the destination account before the corresponding record import begins. Text, number, date, and picklist field types are supported; list fields migrate as multi-select picklists.