Migrate from GENIEE to Salesforce Sales Cloud

GENIEE SFA/CRM Contacts map to either Salesforce Lead or Contact based on the customer's qualification status definition. Unqualified prospects with no associated Account or open Deal map to Salesforce Lead. Qualified buyers attached to an Account map to Salesforce Contact. We inspect the SFA/CRM contact's deal association, lead score, and lifecycle stage during the scoping discovery to define the split rule for this customer specifically. The original GENIEE contact ID and any Japanese field labels are preserved in custom fields for audit and reconciliation.

GENIEE SFA/CRM Company records map directly to Salesforce Account. The Account is the parent record for Contact migration, so we create all Accounts first in dependency order. Japanese regional conventions for address fields (prefecture, city, building) map to standard Salesforce address compound fields with the original Japanese text preserved in a custom field for verification.

GENIEE SFA/CRM Deals map to Salesforce Opportunity. Each GENIEE pipeline becomes a Salesforce Record Type with a corresponding Sales Process that whitelists the tenant-specific stage values. Stage probability percentages migrate from GENIEE to Salesforce StageProbability. Closed-Won and Closed-Loss reasons from GENIEE custom fields map to Loss Reason and custom Win Reason fields.

GENIEE pipeline stages are tenant-defined and vary by customer configuration. We discover the full stage list during scoping, map each to a Salesforce StageName value, and configure a corresponding Sales Process in Salesforce that restricts the stage picklist to only those values relevant to each Record Type. Stage order and probability percentages are preserved as entered in GENIEE.

GENIEE SFA/CRM User records (owner assignments on Contacts, Accounts, and Deals) map to Salesforce User records matched by email address. Role-based access and team hierarchy from GENIEE are documented for the customer's Salesforce admin to reconfigure as Profiles, Permission Sets, and Role Hierarchy post-migration. We flag any GENIEE Owner without a matching Salesforce User for admin provisioning before production migration.

GENIEE MA Campaigns map to Salesforce Campaign. UTM parameters (utm_source, utm_medium, utm_campaign, utm_content) stored per contact are preserved as custom fields on CampaignMember for attribution analysis. Campaign start and end dates, budget, and status migrate directly. GENIEE MA campaign-to-contact associations map to CampaignMember records.

GENIEE DSP campaign metadata (budget, targeting parameters, ad formats, flight dates, network placements, and KPI optimization settings) has no standard Salesforce equivalent. We export this as a custom object DSP_Campaign__c with fields for campaign_name, start_date, end_date, daily_budget, targeting_geography, targeting_device, ad_format, network, and kpi_goal. DSP campaign performance metrics (impressions, clicks, CTR, spend) are exported as a separate DSP_Performance__c custom object linked to DSP_Campaign__c via lookup.

GENIEE SSP publisher inventory data (slot IDs, floor prices, telco/mobile/desktop classification, ad format availability, and geographic placement) is SSP-specific and does not map to standard CRM objects. We export this as a custom object SSP_Inventory__c with fields for publisher_name, slot_id, ad_format, device_targeting, floor_price_cpc, and inventory_status. This custom object is primarily useful for operations teams migrating to a new ad operations tool; Salesforce reporting on SSP data is limited and customers typically integrate this data into a separate BI platform via MuleSoft.

GENIEE DSP bid logs contain per-impression bid decisions, winning bid amounts, and outcome (won/lost). These are high-volume event records that do not belong in a standard CRM. We export bid log summaries (daily or campaign-level aggregates) as a custom object DSP_Bid_Log__c for historical record. Full granular bid logs are exported as a CSV artifact for loading into the customer's data warehouse or analytics environment, not into Salesforce.

File attachments on GENIEE SFA/CRM Contacts, Accounts, and Deals are exported as binary blobs and re-uploaded to Salesforce as ContentVersion records. ContentDocumentLink records are created to attach each file to its parent record (Contact, Account, or Opportunity) in Salesforce. Original file names, MIME types, and upload timestamps are preserved in ContentVersion fields.

GENIEE SFA/CRM custom fields on Contact records vary by tenant. We discover the full custom property list during scoping, generate a field map that specifies the target Salesforce field API name and data type for each, handle type conversion (Japanese date formats to ISO 8601, picklist text to picklist values, free-text to textarea), and pre-create all custom fields on the Lead or Contact object before migration. Field-level permissions are set to Read-Write for the migration user and adjustable post-migration.

GENIEE SFA/CRM custom fields on Account records migrate to Salesforce custom fields on Account. Department and location data using Japanese regional conventions map to the standard Salesforce address compound field where applicable or to custom text fields where the data does not conform to standard address field structure. Custom picklist values are migrated as Salesforce picklist values with the original Japanese label preserved in a description field for admin reference.

GENIEE SFA/CRM tags on Contacts and Companies use a tenant-defined vocabulary. Tags stored as label arrays are exported and mapped to Salesforce multi-select picklist fields on Contact or Account. Alternatively, the customer may choose to map tags to Salesforce Topics with TopicAssignment records if they plan to use Content Delivery and Experience Cloud features. The choice is made during scoping based on the customer's intended use of tag data in Salesforce.

GENIEE SFA/CRM engagement history (calls, emails, meetings, tasks, and notes) is stored in the engagement subsystem and must be extracted as a separate export from the contact and account records. We map task engagements to Salesforce Task with Status, Priority, and ActivityDate preserved. Note engagements map to Salesforce Note linked via ContentDocumentLink to the parent Contact, Account, or Opportunity. Activity timeline ordering is preserved by setting ActivityDate to the original GENIEE timestamp.