Migrate from GENIEE to Microsoft Dynamics 365 Sales

GENIEE SFA/CRM Contacts map directly to Microsoft Dynamics 365 Contact. Field naming conventions are documented in Japanese; we use machine-assisted translation and Japanese-speaking data engineers to discover the full field inventory during scoping. Email, phone, name, and owner fields migrate cleanly. Tenant-specific custom properties on Contact are mapped to typed Dynamics 365 fields (text, picklist, number) or custom fields during schema design. Owner assignment is resolved by email match against Dynamics 365 User records.

GENIEE Companies map to Dynamics 365 Account. Regional location data uses Japanese administrative district conventions; we normalize these to standard address formats during transform. Account hierarchy (parent-subsidiary relationships) migrates where present. Website and industry classification fields map from GENIEE Company properties to Account fields.

GENIEE Pipeline Opportunities map to Dynamics 365 Opportunity. Stage names, win/loss probability percentages, and pipeline stage history are preserved as a full stage-traversal audit trail. We map GENIEE pipeline stages to Dynamics 365 Opportunity Sales Process stages, creating a Sales Process per GENIEE pipeline where multiple pipelines exist. Closed-Lost and Closed-Won reasons migrate as custom fields if configured in the GENIEE tenant.

GENIEE Marketing Automation Campaigns map to Dynamics 365 Campaign. Campaign attribution data (UTM parameters, source, medium) stored per Contact is preserved as campaign member custom fields or campaign custom attributes in Dynamics 365. Note that Dynamics 365 Marketing (the separate marketing module) is not required for campaign record migration; Campaign and CampaignMember objects are standard in Sales.

GENIEE DSP campaigns (budget, targeting parameters, ad formats, flight dates) do not map to any standard Dynamics 365 object. We export DSP campaign metadata as a custom entity DSP_Campaign in Dataverse, with fields for budget_amount, targeting_criteria, ad_format, flight_start_date, flight_end_date, and campaign_status. This is SSP/DSP-specific and documented as non-standard CRM data requiring custom entity schema creation before migration.

GENIEE SSP publisher inventory data (slot IDs, floor prices, device classification: telco/mobile/desktop) does not map to standard CRM objects. We export this as a custom entity Publisher_Inventory in Dataverse. Organizations that require this data post-migration should confirm during scoping whether Dynamics 365 is the appropriate home or whether a separate data warehouse is more suitable.

GENIEE SFA/CRM Users assign as record owners. User records (email, name, role) are standard and migrate cleanly by email match against the Dynamics 365 destination User table. Any GENIEE Owner without a matching Dynamics 365 User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Attachments on Contacts, Accounts, and Deals migrate as Dynamics 365 Annotations (notes with file attachments) linked to the parent record. If the organization has enabled SharePoint integration in Dynamics 365, we migrate attachments to SharePoint document libraries and link via ContentDocumentLocation. File size and type limits are validated against Dynamics 365 attachment constraints.

GENIEE SFA/CRM custom fields on Contacts and Accounts are discovered during scoping using Japanese-language field label translation. We generate a field map with type conversion (Japanese date formats to UTC, regional codes to standard picklists, multi-value fields to Dynamics 365 multi-select picklists). The full custom property list is validated in a sandbox migration before production.

GENIEE Contact and Company tags are tenant-defined label vocabularies. We export tags as label arrays and map them to Dynamics 365 custom multi-select picklist fields on the Contact or Account. The customer chooses between a flat multi-select field or Dynamics 365 Topics with TopicAssignment records during scoping.