Migrate from RAMM to Salesforce Sales Cloud

RAMM Client maps 1:1 to Salesforce Account. Client name becomes Account.Name. RAMM's primary contact email on the client record maps to Account.Phone or a custom Primary_Contact_Email__c field. Client-level billing address migrates to Account.BillingAddress. Multi-site clients produce one Account with multiple Site__c records.

RAMM Site has no direct Salesforce equivalent — Salesforce Accounts have addresses but no native site concept. We create a custom Site__c object with a lookup to Account and fields for site name, address, SLA tier, and primary technician. Site IDs are preserved as Source_System_ID__c for traceability.

RAMM contacts at the client level map to Salesforce Contact with a direct AccountId lookup. Contact name, email, phone, job title, and address fields map directly. If the RAMM contact has a site assignment, we create a Site_Assignment__c lookup to the corresponding Site__c record.

RAMM site contacts (primary IT contacts, finance contacts) split into a Salesforce Contact record plus a Site_Assignment__c junction record linking them to the site. This preserves the site-specific contact role without duplicating the Contact. The Site_Assignment__c record stores the role type (IT Admin, Finance, Executive) and allows the same Contact to be assigned to multiple sites. Each junction link is created during migration, preserving the original RAMM relationship.

RAMM Asset objects (hardware inventory, software licenses) require a custom Asset__c object in Salesforce. We create fields for asset tag, make, model, serial number, purchase date, warranty expiry, and a lookup to both Account and Site__c. Asset-to-ticket relationships migrate as a junction object.

RAMM tickets map to Salesforce Case. The RAMM ticket subject becomes Case.Subject, description maps to Case.Description, status maps to Case.Status using a value-mapping table (Open → Open, In Progress → In Progress, Resolved → Closed, etc.). Owner resolves by email match to a Salesforce User.

RAMM links tickets to assets natively. Salesforce Case has no native asset reference, so we create an Asset_Case__c junction object with lookups to Asset__c and Case. Each migrated ticket gets an Asset_Case__c record if it had an asset link in RAMM.

RAMM contracts attach to Client or Site with start/end dates, billing frequency, and value. We map contract value to a Salesforce Opportunity Amount, contract term to CloseDate, and store billing terms as custom Contract__c fields. Multi-site contracts generate one Opportunity per site with the parent contract linked via Custom_Contract__c.

RAMM technicians map to Salesforce Users by email lookup. Unmatched technicians are flagged before migration — teams either invite them as Salesforce Users or reassign their open tickets to a fallback queue. Inactive RAMM technicians map to a default 'RMM Archived' queue.

RAMM file attachments on tickets, assets, and contracts are downloaded and re-uploaded to Salesforce Files (ContentDocument/ContentVersion model). Files are linked to the parent record (Case, Asset__c, or Opportunity) via ContentDocumentLink. File size limits (Salesforce default 25MB per file) are enforced during migration.

RAMM SLA tiers (Bronze, Silver, Gold) are defined per-client or per-site. Salesforce has no native SLA object, so we store SLA tier as a pick-list field (SLA_Tier__c) on the Site__c custom object. Tier labels and response-time definitions are preserved in the field help text for admin reference.

RAMM invoice records have no direct Salesforce equivalent in Sales Cloud — Salesforce Revenue Cloud handles billing separately. We preserve invoice number, amount, date, and status as a custom Invoice__c object linked to the Account for historical reference. Billing automation must be configured in Salesforce Revenue Cloud post-migration.