Migrate from MobileAction to Pipedrive

MobileAction Tracked Apps map to Pipedrive Organizations. The app name becomes Organization name, the app store (App Store or Google Play) becomes a custom ORGANIZATION_TYPE or industry field, and the visibility score becomes a custom numeric field visibility_score__c. App bundle ID or package name maps to a custom field for reference. Organization is created before any related Competitor or Campaign data so that the lookup relationship is satisfied at import time.

MobileAction keyword tracking records map to a Custom Object named App_Keyword. Fields include keyword_text__c, country_code__c, store__c, current_rank__c (integer), search_volume__c (tagged as modeled), difficulty_score__c, and app_id__c (lookup to Organization). This Custom Object requires Pipedrive Advanced tier or above for full API access. Lite plans on Pipedrive can store keyword data in multi-value custom fields on Organization instead, with reduced volume.

MobileAction historical ranking snapshots export as dated rows per keyword-app-country. Each row becomes a Keyword_Snapshot Custom Object record with snapshot_date__c, rank__c, and a lookup to the parent App_Keyword Custom Object. High-volume keyword history requires cursor-based pagination loops from MobileAction's API and chunked inserts into Pipedrive. We batch by 90-day windows to avoid timeout and preserve chronological ordering.

MobileAction competitor visibility scores and ranked keyword lists export as structured Note records attached to the relevant Organization in Pipedrive. The Note title is the competitor app name and the body contains ranked keywords with visibility scores in structured text. The competitor set definition (which apps the user has selected as competitors) is preserved as a named Note so the competitive framing transfers even though Pipedrive has no native competitor benchmark object.

MobileAction SearchAds.com campaign structures map to Pipedrive Deals. Campaign name becomes Deal title, campaign status maps to Deal stage (Active maps to Open stages, Paused and Archived map to Won or Lost), and budget data becomes custom Deal fields. Campaign metadata including ad group structure, automated bid rules, and goal type are stored in custom text fields on the Deal. Deal is linked to the relevant Organization representing the tracked app.

MobileAction CPP metadata — screenshots, promotional text, video URLs, and associated keywords — exports as structured Note records attached to the Organization. The Note captures CPP page ID, associated keywords, creative asset URL references, and performance signals. Raw screenshot and video files are URLs pointing to MobileAction infrastructure and will not persist after account cancellation; we flag these as requiring re-hosting or linking-copy before cutover.

MobileAction ad creative references including impression share and performance signals export as Note records attached to the parent Deal representing the campaign. Creative asset URLs are references, not binary blobs. We export the URL and metadata but flag that URLs may become invalid after account cancellation and should be re-hosted in a persistent asset store if the creative record needs to be preserved long-term.

MobileAction user-level settings including tracked countries, notification preferences, and team member assignments export as configuration metadata. We map tracked countries to custom multi-select fields on Organization, and notification preference flags to custom fields on Deal for campaign-level alerts. Schema varies by MobileAction plan tier; we flag any settings that were plan-gated on the source and document them in the handoff inventory.

MobileAction estimated downloads, revenue, and market share figures are third-party modeled estimates. We import these as custom numeric fields on Organization (estimated_downloads__c, estimated_revenue_usd__c, market_share_pct__c) with an estimation_source__c tag set to MobileAction. We do not treat these as authoritative financial data; the provenance tag flags them for analyst review in Pipedrive's reporting layer.

MobileAction SearchAds.com automated bid and budget rules export as structured condition lists but do not migrate as active automations. Pipedrive's Automation tools have a different trigger-and-action model with no direct equivalent to Apple Search Ads bid rules. We deliver a written inventory of each automation rule with its conditions, actions, and a Pipedrive Automation rebuild recommendation. The customer's admin rebuilds these in Pipedrive's Automation section post-migration.