Migrate from MobileAction to Nutshell

MobileAction Tracked Apps map to a Nutshell Custom Object that we create during migration scope. The Custom Object includes fields for app_id, store (App Store / Google Play), visibility_score, and tracked_country_list. Nutshell's Custom Object supports text, currency, date, and dropdown types but does not support native time-series storage. Historical ranking snapshots per app are exported as a dated CSV archive delivered alongside the migration rather than stored as records.

MobileAction Apple Search Ads campaigns map to Nutshell Deals. Campaign name becomes Deal name, campaign budget maps to a custom currency field campaign_budget__c, and ad group structure is preserved in Deal notes. Goal type ( installs, re-engagement, revenue ) is stored as a dropdown field. The Campaign status (active / paused / archived) maps to the Deal status field. Automated bid rules from MobileAction do not migrate to Nutshell's Deal model; we document them separately for the customer's admin to rebuild as Deal-level tasks or external automation.

MobileAction competitor apps (user-curated sets) map to Nutshell Company records. App name becomes Company name, app store URL becomes Website, and the visibility_score and ranked_keyword_count are stored as custom number fields competitor_visibility_score__c and ranked_keyword_count__c. We preserve the user-curated competitor group as a named list in a custom text field competitor_group__c on each Company. Nutshell has no native competitor benchmarking dashboard, so the competitive context is available as record metadata but requires manual review.

MobileAction CPP metadata (screenshot URLs, video URLs, promotional text, associated keywords) migrates as Nutshell Notes linked to the corresponding Tracked App Custom Object. The raw creative file URLs point to MobileAction's infrastructure and are flagged with an expiration warning since they retire when the MobileAction account closes. We recommend the customer download creative assets before account cancellation.

MobileAction creative assets (screenshot references, video URLs, impression share data) migrate as Nutshell file attachments linked to the corresponding Search Ads Campaign Deal. Impression share percentage and creative performance signals are stored in a custom number field creative_impression_share__c on the attachment note. The raw creative files are URLs, not binary blobs, so we export the URL reference and flag that assets may not persist after account cancellation.

MobileAction keyword ranking history is high-volume time-series data (daily or weekly snapshots per keyword-app-country) that has no native storage equivalent in Nutshell. We export this dataset as a structured CSV archive with columns for app_id, keyword, country, date, rank_position, and search_volume_estimate. The archive is delivered to the customer as a data artifact for import into a analytics platform or spreadsheet. We flag every volume field with an estimation-source tag per MobileAction's data documentation.

MobileAction estimated downloads, revenue projections, and market share figures are third-party modeled estimates. We export these values as a CSV with an estimation_provenance tag and deliver the archive alongside the migration. These metrics do not map to any standard or custom Nutshell field because they represent aggregate market data rather than CRM-record attributes. The customer can link the archive to the corresponding Tracked App Custom Object via a URL field if needed.

MobileAction user-level settings (tracked countries, notification preferences, team member assignments) export as a configuration summary document. We extract the settings blob and map relevant items (tracked_country_list, notification_email_recipients) to Nutshell custom fields on the Tracked App Custom Object or Company records. Automated alert configurations have no Nutshell equivalent and are documented for the customer's admin to rebuild as Nutshell email templates or external automation.