Migrate from Entera to Salesforce Sales Cloud

Entera Investor records map directly to Salesforce Contacts. Investors who represent companies map to Salesforce Contacts with an AccountId pointing to the related Account record. Entera investor type (individual vs. institutional) can be preserved as a custom pick-list field. Additional fields such as email, phone, and mailing address are migrated as standard Contact fields, while the original Entera ID is stored in Source_System_ID__c for traceability.

Institutional investors in Entera — fund managers, REITs, family offices — map to Salesforce Accounts representing the investor entity. Individual investors map to Contacts with a household Account for investors. The mapping also preserves the Entera investor classification as a custom pick-list on the Account record, and any associated custom properties such as fund size migrate to custom fields. For individual investors, the household Account enables grouping of investment contacts.

Entera Properties map to Salesforce Accounts with a 'Property' record type. Property address, type, unit count, and valuation fields migrate to corresponding Account fields or custom fields. Parent property relationships (master property vs. individual units) map via Salesforce ParentId. Property-specific custom fields such as zoning, cap rate, and unit mix migrate to custom fields on the Account, scoped to the Property record type, with page layout assignments for user visibility.

Entera Deals map to Salesforce Opportunities. Deal amount maps to Opportunity.Amount, close date to CloseDate, and stage to StageName via value mapping. If Entera uses multiple pipelines, each pipeline becomes a Salesforce Record Type keyed to a Sales Process. Deal custom fields migrate to Opportunity custom fields, the deal-to-property link becomes Opportunity.AccountId, the primary investor becomes a Contact Role, and original timestamps are preserved as custom datetime fields.

Entera deal pipelines become Salesforce Sales Processes linked to Record Types. Every Entera pipeline requires a corresponding Salesforce Record Type so stage pick-list values and probability weights are scoped correctly per deal category. Pipeline-specific fields such as deal category or funding source are mapped to custom fields on the Opportunity, and each Record Type receives its own page layout and field-level security to match the Entera pipeline’s business rules.

Stage names are mapped value-by-value per Salesforce Record Type. Stage probability percentages and forecast categories are re-applied from Salesforce's stage model. Stage-entered timestamps from Entera are preserved as custom datetime fields for reporting continuity. Inactive or archived Entera stages are stored as custom picklist values for reference, and any custom stage attributes (e.g., exit criteria) are migrated as text fields on the Opportunity to maintain context for future audits.

Any Entera custom investor properties — accreditation status, investment thesis, preferred deal size — require Salesforce custom fields on the Contact object ending in __c. FlitStack creates the field schema before data loads and maps values during the migration run.

Entera property custom fields — zoning classification, cap rate, unit mix — map to custom fields on the Salesforce Account object. Property-specific custom fields are scoped to the 'Property' record type using field-level security so investor-facing layouts remain clean. Each custom field follows the __c naming convention, and picklist values (e.g., zoning districts) are replicated. Validation rules and defaults maintain data quality, while field-level security restricts visibility to internal profiles.

Entera engagement records (emails, calls, meetings, notes) map to Salesforce Tasks, Events, and Notes respectively. Original timestamps, owners, and parent-record links are preserved. Email attachments are re-uploaded as Salesforce Files. Task Subject inherits the Entera email subject, and the Type field reflects the engagement medium. Attachments over 25 MB are flagged for chunked upload. Parent-record links are updated to the migrated Contact, Account, or Opportunity IDs.

Entera's N:N investor-to-property associations require resolution: the primary relationship becomes AccountId on the Contact record; secondary associations are stored in Salesforce Account Contact Relations or a custom junction object depending on whether deal-level attribution is required. The primary role becomes the default Contact Role on the Opportunity, while secondary roles are added with a custom Role__c picklist. Junction objects include fields for investment amount and date to preserve attribution.

Entera documents and attachments on investor or property records are re-uploaded to Salesforce Files linked to the corresponding record. File size limits apply (Salesforce default 25MB per file); larger files are flagged for chunked upload before the migration run. File types PDFs and images are preserved, with the file name stored in Title. ContentDocumentLink records link each file to the parent Contact, Account, or Opportunity, with sharing set to Viewer.

Entera owner IDs are resolved against Salesforce Users by email address match. Unmatched owners are flagged before migration so the team can invite them to Salesforce or assign records to a fallback owner. No record lands without a valid Salesforce OwnerId.