Migrate from Rubi CRM to Zoho CRM

Rubi CRM Contacts map directly to Zoho CRM Contacts. Standard fields (Name, Email, Phone, Address) migrate 1:1. We resolve any custom contact properties discovered during scoping against Zoho's field type inventory and create matching custom fields before import. The Contact-Company relationship maps via the Rubi CRM Company name lookup to the Zoho Account Lookup field.

Rubi CRM Company records map to Zoho CRM Accounts. Company name is the primary dedupe key. Billing and shipping addresses migrate to the Account's address fields. We explicitly map the Company-Contact relationship by name-matching or by cross-referencing Rubi CRM's internal relationship table during export when no foreign key is exposed.

Rubi CRM Member records do not have a direct Zoho CRM equivalent. We map Member ID, member status, and tier name to custom fields on the Zoho Contact record (rubi_member_id__c, rubi_member_status__c, rubi_tier__c). We perform a name and email match to link each Member to its corresponding Contact record before applying the membership custom fields. Rubi CRM does not export full subscription history in a single export pass, so we document renewal date and tier name from the active Membership record.

Individual Membership records (start date, end date, tier, renewal amount) attach to the Member and therefore to the Contact via rubi_membership_start__c, rubi_membership_end__c, and rubi_tier__c custom fields. We map the primary active membership; historical membership records are documented in a written inventory for the customer's admin to append to the Contact as additional custom fields if required. Tier names are preserved as string values for post-migration mapping in Zoho.

Rubi CRM Events map to Zoho CRM Events with Event Title, Start DateTime, End DateTime, Location, and Description preserved. We map the Rubi CRM Event record to the Zoho Event and link attendee Contacts via EventRelation records resolved by email match. Event status (Confirmed, Cancelled, Postponed) migrates to a Zoho custom Event Status picklist.

Rubi CRM Training bookings are child records tied to a Contact or Member. We map each booking as a Zoho Task with the Training course name in the Subject, the booking date as ActivityDate, and the status (Registered, Attended, No-show, Cancelled) as a custom Task field rubi_booking_status__c. For instructor-led Training with a specific time slot, we map to a Zoho Event instead. The parent Contact is resolved by email or name lookup before Task or Event insert.

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 names, their ordering, and probability values during the scoping call. We deliver a written Pipeline Configuration Brief listing each Rubi CRM stage and its recommended Zoho Deal Stage equivalent with probability weight. The customer's admin creates the Zoho pipeline and stages post-migration using this brief.

Rubi CRM Deal records map to Zoho CRM Deals. Deal name, amount, expected close date, and the pipeline stage custom field value migrate to Zoho Deal fields. We look up the stage value against the stage mapping defined in the Pipeline Configuration Brief and set the Zoho Stage field accordingly. Owner mapping resolves by email against Zoho Users.

Rubi CRM Activity records logged via the Outlook plugin (email subject, body text, timestamp, linked Contact) map to Zoho CRM Tasks with activity type recorded in a custom field. Thread-level email threading from the original Outlook message is not preserved in Rubi CRM's export, so we migrate the activity timestamp, subject, and body as a Task note. Full email body content migrates to Zoho Tasks with the original email text in the Description field.

Rubi CRM Tasks map directly to Zoho CRM Tasks with Subject, Status, Priority, Due Date, and Owner preserved. Owner resolution uses email match against Zoho Users. Any Rubi CRM Task assigned to an owner without a Zoho User match is held in the owner reconciliation queue for the customer's admin to provision the user before import resumes.

Rubi CRM custom fields per record type are discovered during the export scoping phase. We inspect the exported column headers to identify non-standard fields, infer their data type from value patterns (date, number, picklist), and create matching custom fields in Zoho CRM via the Setup > Fields interface before migration begins. Custom fields without a clear type are created as text fields and flagged for post-migration review.

Rubi CRM's Report Builder exports flat data snapshots and its Audit Log tracks user actions. Neither is a transactional record store. We do not migrate these objects. We deliver a written inventory of Saved Report names and column definitions for the customer's admin to re-create as Zoho Reports or Zoho Analytics views post-migration.