Migrate from MobileAction to Twenty CRM

MobileAction tracked apps map to Twenty CRM Company records, with the app store (App Store or Google Play), app bundle ID, and visibility score stored as custom fields on the Company. The app publisher's organization name becomes the Company name, and we preserve the app icon URL and current visibility score as reference fields. This establishes the parent record for all ASO data related to each app title.

Publisher and developer contacts associated with tracked apps in MobileAction map to Twenty CRM People records. We extract contact names, roles, and email addresses from MobileAction campaign and CPP association data where available, and link each Person to the corresponding Company record. People records without a resolvable Company link are stored with a NULL Company reference and flagged for manual review during cutover.

MobileAction keyword tracking data (keyword text, search volume estimates, difficulty scores, associated countries) maps to a Keyword custom object in Twenty CRM. We create the custom object with fields for keyword text, estimated monthly volume, difficulty index, and a Country multi-select. The Keyword object links to the Company record for the tracked app via a lookup relationship, making it possible to query keyword performance by app.

Daily and weekly keyword ranking snapshots export as dated rows from MobileAction and map to a Keyword Ranking custom object in Twenty CRM with fields for ranking date, position, previous position, delta, and the associated Keyword lookup. This is the highest-volume dataset in a typical MobileAction export. We chunk exports into monthly batches, ordered by date, and insert in date-sequence to preserve chronological ordering in Twenty CRM.

Each user-curated competitor app in MobileAction maps to a Competitor custom object in Twenty CRM. We preserve the competitor app name, bundle ID, store, visibility score, and the user-defined competitor group name as a text field. The Competitor object links back to the owning tracked app Company record. Note that MobileAction competitor sets are user-defined rather than universal, so the competitive framing is preserved but coverage depends entirely on the customer's original MobileAction configuration.

Apple Search Ads campaign structures from MobileAction map to Twenty CRM Opportunity records. The campaign name becomes the Opportunity name, and we store campaign status, budget, and goal type as custom fields on the Opportunity. Ad group structures export as child records linked via a Custom Object (Ad Group) with a lookup to the parent Opportunity. This mapping treats campaigns as sales pipeline proxies for ad spend tracking rather than native Apple Ads integrations.

CPP metadata from MobileAction (page ID, associated keywords, screenshot references, promotional text, video URLs) maps to a Custom Product Page custom object in Twenty CRM. Each CPP record links to the parent Company (the app it belongs to) and preserves the page association keywords. We store the CPP ID from MobileAction as a reference field to maintain traceability back to the source.

Ad creative asset references (screenshots, video URLs, impression share data) from MobileAction export as Ad Creative custom objects in Twenty CRM linked to the parent Opportunity (campaign). The creative asset URLs point to MobileAction infrastructure and are flagged for re-hosting or reference-copy before account cancellation. We export the URL, creative type, and any performance signals stored in MobileAction, and set a re-host flag on each record.

Estimated downloads, revenue projections, and market share estimates from MobileAction (which are third-party modeled figures, not first-party App Store data) export to an App Intelligence custom object in Twenty CRM. We tag every numeric field with an estimation-source field so downstream analysts can apply confidence weighting. These values do not reconcile to App Store Connect or Play Console figures because they are modeled approximations.

Automated bid and budget rules from MobileAction SearchAds.com modules are not migrated as executable code. We export the rule conditions, goal categories, and action definitions as records in a Configuration custom object and deliver a written inventory document mapping each rule to a recommended Twenty CRM workflow rebuild (using Tasks and Notes as a lightweight replacement). The customer or a Twenty implementation partner rebuilds the automation logic in Twenty after migration.