Migrate from GP Flow to Salesforce Sales Cloud

Individual investors in GP Flow map directly to Salesforce Contacts. Email address serves as the unique identifier for owner resolution. Mailing address, phone, and investor classification fields migrate with direct field mapping. Individual investors linked to entity investors require Account association in Salesforce.

Entity investors (LLCs, family offices, institutions) map to Salesforce Accounts. GP Flow's entity name becomes Account.Name; entity type (LLC, LP, Trust) maps to a custom Industry or Type pick-list value. Entity investors may have multiple individual contacts as signatories—these become Contacts with Account lookup to the entity Account.

If GP Flow funds map to Salesforce Opportunities with Fund Name as Opportunity.Name and Fund Size as Amount, we use the standard Opportunity object. For complex fund structures with multiple closes or capital calls, a Fund__c custom object better preserves fund-level data; each capital call becomes a related Opportunity or custom Transaction__c record.

Capital contributions have no Salesforce standard equivalent. We create a Transaction__c custom object with lookup to the investor Contact and the fund Opportunity. Contribution amount, date, wire reference, and contribution type (equity, debt, preferred) migrate as custom fields. Historical contributions preserve original dates as custom datetime fields since Salesforce CreatedDate reflects migration time.

Capital calls trigger investor obligations. Each call maps to an Opportunity update (Stage changes to 'Capital Call Issued') with a custom Capital_Call_Date__c timestamp, or to a separate Transaction__c record with type 'Capital Call'. Investor notification status migrates as a custom field for follow-up in Salesforce.

Fund distributions to investors map to Transaction__c records with type 'Distribution'. Amount, date, distribution type (return of capital, profit distribution, preferred return), and recipient investor all migrate as fields. GP Flow distribution history preserves original dates for IR continuity. The Transaction__c record also records the distribution method, such as wire or check, to support reconciliation.

GP Flow investor email history migrates as Salesforce Tasks with Type = 'Email'. Original subject, body, and timestamp preserved. Task links to the relevant investor Contact and fund Opportunity. Rich-text formatting in emails transfers to Salesforce's activity formatting. Attachments from the original emails are stored as Salesforce Files linked to the Task, preserving the complete communication record.

Investor meetings and calls migrate as Salesforce Events with original start/end times preserved. Event links to the investor Contact and the fund Opportunity. Meeting notes migrate as Salesforce Notes attached to the Event record. Recurring meeting series are broken into individual Event records, each preserving the recurrence pattern as a custom field for reference.

GP Flow stores investor agreements, subscription documents, and fund legal files. Documents migrate as Salesforce Files (ContentVersion). Files attach to the relevant Contact (for investor-specific docs) or Opportunity (for fund-level docs). GP Flow version history surfaces as Salesforce ContentVersion version tracking.

GP Flow tracks investor onboarding stage (Accredited Verification, AML/KYC, Subscription Signed). This data becomes a custom pick-list field (Investor_Onboarding_Status__c) on Contact. Firms using Salesforce Leads for prospective investors map this to Lead.Status with value mapping for each onboarding stage. The pick-list values include 'Pending Verification', 'Verification In Progress', and 'Completed' to reflect the full lifecycle.

GP Flow fund performance metrics (IRR, MOIC, DPI) have no direct Salesforce equivalent. These values migrate as custom number fields on the Fund__c or Opportunity object for reference. Full fund performance reporting requires Salesforce Analytics (Tableau) or custom report builder configuration post-migration.

GP Flow internal users map to Salesforce Users by email address match. Unmatched users are flagged before migration; the team either provisions Salesforce licenses first or assigns records to a fallback user. GP Flow role/permissions do not transfer—Salesforce profiles and permission sets handle access control post-migration.