Migrate from MobileAction to Freshsales

MobileAction Tracked Apps export as Freshsales Product records. The app store (App Store or Google Play), app bundle ID, and current visibility score migrate as Product fields. We preserve the visibility_score as a custom numeric field on the Product so sales and growth teams can reference ASO health alongside deal context. App name becomes Product Name; bundle ID becomes Product Code.

MobileAction keyword tracking data (ranking positions, search volume estimates, difficulty scores per app-country pair) migrates to a custom object named App Keyword. Each record carries the keyword text, country, associated app Product lookup, current rank, volume estimate, difficulty score, and a date stamp. Volume data is flagged as a modeled field using the estimation_source__c tag. Keyword histories require a separate dated row per snapshot, creating a time-series custom object with unique_id combining keyword_id and snapshot_date.

Historical daily or weekly ranking snapshots per keyword-app-country export as dated rows in a Keyword Snapshot custom object. This is a high-volume dataset — we chunk exports by date range, use cursor-based pagination against the MobileAction Dashboard API, and insert in batches of 500 records per API call to avoid timeouts. Snapshot records link to the parent App Keyword and the Product (Tracked App) for cross-object filtering in Freshsales reports.

MobileAction user-curated competitor sets migrate as a Competitor Set custom object containing a name, description, and the list of competitor app bundle IDs. Each competitor app reference creates a separate Competitor App record linked to the Competitor Set. The competitor keyword visibility score and ranked keyword list migrate as a Note attached to the Competitor Set for reference without creating a full product catalog in Freshsales. The destination platform does not automatically replicate competitive benchmarking coverage.

MobileAction SearchAds.com campaign structures export as Freshsales Deal records. Each campaign becomes a Deal with the campaign name, country targeting, and status. Budget allocation and spend data migrate to custom currency fields on the Deal. If multiple ad groups exist under a campaign, each ad group becomes a separate Deal with a parent Deal lookup, creating a campaign-adgroup hierarchy within the Freshsales pipeline.

CPP metadata including screenshots, promotional text, videos, and associated keywords migrates to a custom object named Custom Product Page. The page ID and app association (Product lookup) transfer so the destination can reconstruct the CPP relationship. Screenshots and video URLs are exported as URL references — we flag that these URLs point to MobileAction infrastructure and may not persist after account cancellation, recommending the customer download creative assets before migration.

Creative asset references (screenshot URLs, video URLs) with impression share and performance signals migrate as Notes attached to the corresponding Apple Search Ads Deal. The Note body contains the asset URL, performance metric (impression share percentage), and asset type. We export the URL reference only — raw creative files are not binary blobs in MobileAction and must be re-downloaded from the original source or the MobileAction creative library before account cancellation.

Estimated downloads, revenue, and market share figures from MobileAction migrate to a custom object named App Intelligence with an estimation_provenance__c tag marking the data as third-party modeled. Each record is dated (snapshot_date__c) and linked to the associated Product. We recommend customers treat these figures as directional for financial planning and use first-party data from App Store Connect or Play Console for precise attribution.

SearchAds.com automated bid and budget rules export as structured conditions in a written inventory document. Goal categories (six types) and rule conditions are catalogued with their current configuration and a recommended Freshsales Workflow equivalent. The destination admin rebuilds these as Freshsales Workflows manually because automation rule structure does not map between platforms. We do not migrate automation rules as executable code.

User-level settings including tracked countries, notification preferences, and team member assignments export as configuration records in a Dashboard Configuration custom object. The settings schema varies by MobileAction plan tier — we flag any settings that were plan-gated and note which custom object fields were created as a result. The configuration blob serves as a reference record rather than an active setting that applies in Freshsales.