Migrate from MobileAction to Microsoft Dynamics 365 Sales

Apps tracked in MobileAction (app ID, name, store, visibility score) migrate to a custom MobileApp__c entity in Dynamics 365. We create the entity during schema design, including fields for appId, store, appName, visibilityScore, and lastFetchedDate. Each MobileApp__c record is associated to an Account record when the app belongs to a known publisher that exists in Dynamics; otherwise it is associated to a placeholder Account created during migration.

Keyword tracking data (keyword text, country code, search volume estimate, difficulty score) migrates to AppKeyword__c linked to the parent MobileApp__c record via Lookup. The searchVolume and difficultyScore fields are tagged with a custom field EstimatedSource__c set to 'MobileAction_modeled' to indicate these are third-party approximations and not authoritative first-party data.

Daily or weekly ranking snapshots (keyword ranking position per app-country-date) migrate to KeywordRanking__c as dated rows linked to AppKeyword__c. This is the highest-volume dataset in a MobileAction export — we chunk exports into date-bounded batches and use cursor-based pagination loops against MobileAction's Dashboard API to avoid timeouts during extraction. Batch ordering is preserved in the migration job so that the timeline is complete and sequential in Dynamics 365.

Competitor visibility scores and ranked keyword lists export from MobileAction and migrate to CompetitorApp__c. The competitor set definition (which apps the user selected as competitors) is preserved as a named CompetitorSet__c field and replicated as a list-view filter in Dynamics 365 so the competitive framing transfers without requiring manual re-curation. Any competitor app that also appears as a tracked app in the source resolves to the same MobileApp__c record.

Campaign structures, ad group assignments, and goal configurations from MobileAction's SearchAds.com modules migrate to SearchAdsCampaign__c. Goal category names (MobileAction's 6 goal types) are mapped to text fields and documented in the migration mapping sheet for the admin to reconcile against any Microsoft Dynamics 365 Sales campaign features in use. Bid rules and automated pacing settings do not migrate as active configurations — they are listed in the automation inventory deliverable.

CPP metadata (screenshot URLs, promotional text, video links, associated keywords) migrates to CPPPage__c with the page ID, app association, and keyword list preserved as structured fields. The creative asset URLs (pointing to MobileAction infrastructure) are exported as-is and re-hosted or link-copied during migration so that the destination retains a record of what was tracked. Raw visual assets (screenshot files) migrate to a dedicated SharePoint document library associated to the app record.

Estimated downloads, revenue, and market share figures from MobileAction migrate to AppMetrics__c with a mandatory Provenance__c field set to 'MobileAction_ThirdPartyEstimate'. We flag every numeric volume field with this tag so that analysts querying Dynamics 365 know the data is modeled and not authoritative for financial planning or budget attribution. Customers should use App Store Connect and Google Play Console for first-party figures.

User-level settings including tracked country list, notification preferences, and team member assignments migrate as JSON configuration blobs stored in a MASettings__c text field. These are plan-tier-dependent — Lite plan settings migrate at Lite coverage levels. We flag any setting that was gated by a higher plan tier so the customer knows which configuration options require a plan upgrade to re-enable.