Migrate from RAYNET CRM to Salesforce Sales Cloud

RAYNET Contact records map to Salesforce Contact. Standard fields (Name, Email, Phone, Address) map directly. The RAYNET GPS latitude and longitude derived from contact address for Map Analysis migrate to Salesforce custom fields (Latitude__c, Longitude__c) on the Contact record. Custom Contact properties from RAYNET extract via list export and map to Salesforce custom fields or store as generic CustomProperty__c JSON blobs if no direct type match exists. Contact is imported after Account to satisfy the AccountId Lookup.

RAYNET Company records map to Salesforce Account. The company address becomes the Account's BillingAddress and ShippingAddress fields. Contact address data and any GPS coordinates derived from company address migrate to corresponding Account custom fields. We sequence Accounts before Contacts to maintain the r-1 relationship integrity during import. If RAYNET Companies have no linked Contacts, they import as standalone Accounts.

RAYNET Deal records map to Salesforce Opportunity. Deal value maps to Amount, estimated close date to CloseDate, and probability to the StageName field after stage mapping is applied. OwnerId resolves by matching the RAYNET deal owner email to the Salesforce User table. Deals without an associated Account or Contact are held in a staging queue until the parent record is resolved.

RAYNET pipeline stages (stage names, order, and probability percentages) are extracted from the pipeline configuration and mapped to Salesforce Opportunity Stage values. Stage probability percentages migrate to StageProbability on each stage entry. If the customer has multiple pipelines in RAYNET ENTERPRISE, each pipeline becomes a Salesforce Record Type with its own Sales Process whitelisting the stage values.

RAYNET multiple pipelines (ENTERPRISE tier only) map to Salesforce Opportunity Record Types. Each Record Type gets a corresponding Sales Process that controls which stage values are available for that pipeline. START and PROFESSIONAL tiers with a single pipeline map to a default Opportunity Record Type and Sales Process without additional configuration.

RAYNET call activities map to Salesforce Task with TaskSubtype set to Call. Call duration, disposition, and outcome from RAYNET customise to Task fields. Activity timestamps preserve on ActivityDate for timeline ordering. The WhoId on Task links to the migrated Contact or Lead; WhatId links to the related Account or Opportunity.

RAYNET email activities migrate to Salesforce EmailMessage records (the email content and headers) linked to a Task record (the activity timeline entry). Subject, body, and sender/recipient addresses transfer. The WhoId on Task points to the migrated Contact or Lead; WhatId points to the related Account or Opportunity. EmailMessage Body preserves as plain text or HTML depending on the destination org's configuration.

RAYNET meeting activities map to Salesforce Event with StartDateTime, EndDateTime, Subject, and Location preserved. Attendees from RAYNET link to EventRelation records pointing at the migrated Contacts, Leads, and Users. Meeting notes migrate as Event Description.

RAYNET general task activities (non-call, non-email, non-meeting) migrate to Salesforce Task. Status, Priority, Subject, and ActivityDate preserve. Assignment resolves by matching RAYNET owner email to Salesforce User. Tasks without a resolved WhoId are linked to the parent Account or Opportunity via WhatId.

RAYNET Sales Order records map to Salesforce Order. Subject, Final Price, Status, Estimated Costs, and Delivery Date map to their Salesforce Order equivalents. Shipping and billing address fields on the RAYNET Sales Order map to Salesforce Order ShippingAddress and BillingAddress. We sequence Order creation after Account and before Opportunity to maintain the OrderAccountOpportunity relationship chain.

RAYNET Quote records linked to Deals map to Salesforce Quote. Validity dates, line-item pricing, and quote body require field-level mapping because Quote schema varies between CRMs. Quote PDFs and any attached documents migrate as ContentDocument linked via ContentDocumentLink to the Quote record. Quote is activated status-flagged in Salesforce only if the RAYNET quote was in a comparable sent or accepted state.

RAYNET User records with deal ownership assignments map to Salesforce User records. We resolve by email match. Any RAYNET Owner without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes, because OwnerId is a required reference on Opportunity and other objects.

RAYNET custom fields on Contact extract via list export with their data types. We map each to an equivalent Salesforce custom field on Contact, using Salesforce field type matching (text, number, date, picklist, checkbox). Fields with no direct Salesforce equivalent store as custom text fields or JSON custom properties depending on the customer's preference during scoping.

RAYNET custom fields on Company (Account) migrate to Salesforce Account custom fields using the same type-matching approach. GPS coordinates derived from account address are stored as Latitude__c and Longitude__c custom fields on Account to preserve the Map Analysis data in the destination org.

RAYNET tags on Contacts and Deals extract as label arrays. Tags migrate to Salesforce as multi-select picklist fields on the respective object if the destination org has fewer than 150 distinct tag values per object. Tags exceeding that threshold migrate to Salesforce Topics with TopicAssignment records. The customer selects the tag strategy during scoping.

Files attached to Contacts, Accounts, Deals, and Activities in RAYNET export via XLSX export or API where available. We re-associate each file to the correct record in Salesforce using record ID cross-reference tables generated during migration. Attachments attach as ContentVersion records linked via ContentDocumentLink to the parent Contact, Account, Opportunity, or Task.