Migrate from Real Intelligence to Salesforce Sales Cloud

Direct map to Salesforce Contact. Real Intelligence contacts without a primary company link are attached to a default 'Unassigned' Account record or routed to Lead based on deal-stage criteria. The Contact.AccountId lookup requires an existing Account — we sequence Accounts first in every migration run.

Real Intelligence companies map to Salesforce Accounts. Parent-child company hierarchies in Real Intelligence translate to Account.ParentId. Multi-company associations on a single contact collapse to one primary AccountId lookup plus Account Contact Relationships for secondary links. We preserve the original industry and billing address fields from the source company for continuity in reporting.

Real Intelligence deals map to Salesforce Opportunities. Each deal's pipeline becomes a Salesforce Sales Process keyed by RecordTypeId. Stage names map value-by-value per record type. CloseDate, Amount, and OwnerId carry over directly once owner resolution completes. If the deal includes custom fields, those map to Opportunity __c fields after RecordTypeId is set.

Real Intelligence's pipeline object becomes both a Salesforce Record Type and a Sales Process. We create one record type per pipeline so stage pick-list values are scoped correctly per deal type. The record type name and label are derived from the pipeline name.

Stage names map value-by-value from Real Intelligence to Salesforce Opportunity Stage values. Each mapping is scoped to a record type. Stage probability and forecast category are reapplied from Salesforce-side defaults unless you specify custom probability curves per stage. Custom stage labels can be retained by creating matching values in the Opportunity StageName picklist.

Real Intelligence engagement records (calls, emails, meetings) map to Salesforce Task and Event objects. Task.Type = 'Call' or 'Email' for calls and emails; Event for meetings with original start/end times preserved. ParentWhatId links to the related Opportunity or Contact. All timestamps use UTC to maintain consistency across time zones.

Real Intelligence notes migrate as Salesforce Notes (modern Notes object). File attachments re-upload to Salesforce Files (ContentDocument/ContentVersion). Inline images in notes are downloaded and rehosted in Salesforce's file storage. Salesforce's 25MB per-file limit applies. If a note contains embedded links, we replace them with relative URLs pointing to the new Salesforce record.

Real Intelligence custom fields on contacts become Salesforce custom fields with __c suffix. We map the source field type to the closest Salesforce type (text, number, picklist, date, checkbox). All custom fields must be pre-created in Salesforce before the migration validates field-level data.

Deal-level custom properties migrate to Opportunity __c fields. Salesforce requires RecordTypeId to be set before field-level validation can enforce pick-list values — we handle this sequencing automatically during the migration run. All custom field values are validated against the target picklist before insert to avoid runtime errors.

Real Intelligence custom objects map 1:1 to Salesforce custom objects. N:N relationships between custom objects in Real Intelligence require Salesforce junction objects. We surface these in the migration plan and create the junction object schema as part of the Salesforce-side setup phase.

Real Intelligence owner IDs resolve to Salesforce User records via email address matching. Unmatched owners are flagged before migration so your team can either invite them to Salesforce first or assign their records to a fallback owner. No Opportunity or Contact lands without an OwnerId.

Real Intelligence workflow definitions, sequences, and automation rules do not have a direct equivalent in Salesforce. We export them as JSON reference files for your Salesforce admin to rebuild using Flow and Process Builder post-migration. The exported JSON includes condition logic, action steps, and entry criteria to guide the rebuild.