Migrate from MobileAction to Salesforce Sales Cloud

MobileAction's tracked app list (app ID, name, store, visibility score, estimated downloads, estimated revenue) maps to a Salesforce custom object we provision as App__c. App store platform (App Store / Google Play) maps to a picklist field; visibility_score__c maps to a number field with the original MobileAction scale preserved. Estimated download and revenue fields carry an is_modeled__c flag set to true, pointing to MobileAction as the estimation source.

MobileAction keyword tracking data (keyword, country, app ID, ranking_position, search_volume_est, difficulty_score) maps to App_Keyword__c with a lookup relationship to App__c. Ranking position migrates as integer rows per date. Search volume estimates and difficulty scores carry is_modeled__c = true. We chunk keyword exports by country and date range to handle cursor-based pagination without timeouts on accounts with hundreds of thousands of keyword rows.

Daily or weekly ranking snapshots export from MobileAction as dated rows per keyword-app-country. We flatten these into Keyword_Ranking__c records with ranking_date__c, position__c, and a lookup to App_Keyword__c. This is the highest-volume dataset in the migration; we batch exports by 90-day windows and write into Salesforce via Bulk API to avoid API timeout errors.

MobileAction's competitor visibility scores and ranked keyword lists export per user-curated competitor set. We preserve the competitor set name as a text field (competitor_set_name__c) and migrate each competitor app as a Competitor_App__c record with visibility_score__c and keyword_count__c. The destination does not automatically replicate the same competitive coverage; we deliver a named list document so the customer's admin can extend the set post-migration.

SearchAds.com campaign structures export from MobileAction's campaign management modules. We map campaign_name__c, campaign_status__c, campaign_budget__c, campaign_goal_type__c (6 named goal categories from MobileAction), and campaign_start_date__c into Apple_Ads_Campaign__c with a lookup to App__c. Ad group assignments and keyword-to-campaign mappings migrate as separate Apple_Ads_Ad_Group__c records with a lookup to the campaign.

Ad groups within each SearchAds.com campaign migrate as Apple_Ads_Ad_Group__c with a lookup to Apple_Ads_Campaign__c. Ad group name, status, default bid, and match type map to custom fields. Keywords within each ad group migrate as Apple_Ads_Keyword__c with a lookup to Apple_Ads_Ad_Group__c.

MobileAction SearchAds.com automated bid and budget rules export as structured condition blocks with named goal categories. We deliver a written inventory of each rule's trigger conditions, bid adjustments, and goal type mapping with a recommended Salesforce Flow equivalent. Rules do not migrate as code because SearchAds.com rule semantics do not map to Salesforce Flow triggers; the customer's admin or a certified Salesforce partner rebuilds them post-migration.

CPP metadata (page ID, app association, screenshot URLs, promotional text, video URL, associated keywords) exports via MobileAction's CPP Intelligence API. We create a ContentWorkspace record per app and migrate CPP metadata into CPP_Variant__c with screenshot_url__c, video_url__c, and keywords__c as text fields. The raw creative files are URL references — if the URLs point to MobileAction infrastructure, we flag them for re-hosting before insert.

Creative asset references (creative ID, impression share, performance signals) map to Ad_Creative__c with a lookup to Apple_Ads_Campaign__c or Apple_Ads_Ad_Group__c. MobileAction stores creative files as URLs, not binary blobs. We export the URL reference and flag any that were hosted on MobileAction infrastructure for re-hosting or re-linking before account cancellation.

Estimated downloads, revenue, and market share figures export with an explicit estimation_provenance__c tag set to MobileAction and an is_modeled__c flag set to true. We map these into App_Intelligence__c with period_start__c, period_end__c, estimated_downloads__c, estimated_revenue__c, and market_share__c fields. Downstream analysts apply their own confidence weighting using the provenance tag.

User-level settings (tracked countries, notification preferences, team member assignments) export as configuration blobs. Schema varies by plan tier, so we flag any settings fields that were plan-gated and document whether they require a plan upgrade to export. Settings migrate as JSON or key-value pairs stored in a Long Text Area field for manual reconstruction in Salesforce.

The list of countries tracked per app in MobileAction migrates as App_Country__c with a lookup to App__c and country_code__c as a text field. This preserves the per-app country scope from MobileAction and ensures the destination reflects which markets were being monitored without requiring manual reconfiguration in Salesforce.