Migrate from REDA to Salesforce Sales Cloud

REDA Contact records map 1:1 to Salesforce Contact. Email is the primary lookup key. Contacts without a primary company link to a default placeholder Account in Salesforce. Owner resolution uses email match against destination Salesforce users; unmatched owners are flagged before migration commits.

REDA Company maps to Salesforce Account. Company name maps to Account.Name, domain maps to Account.Website. REDA parent-company hierarchies map to Account.ParentId — the parent must be migrated first, and circular references are flagged during validation. Multi-company associations that REDA supports N:N collapse to the primary AccountId plus Account Contact Relations.

REDA Deal maps to Salesforce Opportunity. Deal name becomes Opportunity.Name, amount becomes Opportunity.Amount, close date becomes Opportunity.CloseDate. Deal stage maps to Opportunity.StageName via a value_mapping defined per deal pipeline. Pipeline and stage names in REDA become Salesforce Sales Process and Stage pick-list values scoped to the Opportunity's record type.

REDA's Property custom object does not have a native Salesforce equivalent. The migration creates Salesforce custom fields on the Opportunity object — Property_Type__c, Property_Status__c, Square_Footage__c, Unit_Count__c — to preserve property context within the deal record. This loses REDA's parent-child Property hierarchy; teams needing hierarchy modeling rebuild it as Salesforce custom objects with lookup relationships.

REDA Units belong to Properties and carry lease status, unit type, and rent amount. Since Salesforce has no native Unit object, unit-level detail is split across multiple custom fields on the parent Opportunity record. Units with unique identifiers are preserved as a text field listing all associated unit numbers; if unit detail must be individually tracked, a Salesforce custom Unit object with a lookup to Opportunity is created post-migration.

REDA's Project object carries construction timelines, phase statuses, and compliance data. Salesforce does not have a native Project object in Sales Cloud. FlitStack creates a Custom_Project__c object in Salesforce with fields for Phase__c, Compliance_Status__c, Target_Completion__c, and a lookup to the primary Opportunity. This preserves project context without conflating construction data with sales pipeline stages.

REDA activities attach to Properties or Units, not directly to Contacts. Salesforce requires Tasks and Events to attach to Contact or Opportunity records. FlitStack creates a Property_Activity__c junction object that links the Task/Event to both the Opportunity and the REDA Property identifier, preserving the property context while satisfying Salesforce's attachment model.

REDA Budget records track line items, approval statuses, and phase-gate amounts per Project. Salesforce has no native budget object. FlitStack creates a Budget__c custom object with Amount__c, Phase__c, Approval_Status__c, and an Opportunity__c lookup, preserving budget amounts and phase associations. Approval logic must be rebuilt in Salesforce Flow using Approval Processes.

REDA compliance records document inspections, permits, and regulatory approvals per project. These migrate to a Salesforce custom object Compliance__c with Status__c, Type__c, Issued_Date__c, and an Opportunity__c lookup. The approval routing and automatic status-update logic REDA handles natively must be rebuilt in Salesforce Flow.

REDA file attachments on Properties, Units, or Projects are downloaded and re-uploaded to Salesforce Files, linked to the corresponding Salesforce record (Opportunity or custom object). File size limits apply — Salesforce defaults to 25MB per file. Inline images in notes are extracted, re-hosted, and re-embedded in Salesforce Notes.

REDA owner IDs are resolved to Salesforce User records by email address match. Records whose owners have no matching Salesforce User are flagged before migration commits — teams either create Salesforce User records for those owners or assign their REDA records to a fallback Salesforce user designated by the admin.