Migrate from MobileAction to Mailchimp

Each Tracked App in MobileAction (app ID, app name, store, visibility score, estimated downloads) maps to a Mailchimp Audience with a tag representing the app name and store. The visibility score and estimated download range store as merge fields on a reference contact or as notes on the Audience. Mailchimp does not have a native app record object, so the app intelligence data becomes reference metadata attached to the Audience rather than a standalone entity.

Keyword tracking data (keyword text, search volume estimate, difficulty score, ranked position per country) maps to Mailchimp merge fields using a keyword identifier as the field name and the volume or difficulty score as the value. We preserve the modeled-volume provenance tag because MobileAction's keyword volume figures are third-party estimates. High-priority keywords become tags on the relevant Audience member records so the team can filter sends by keyword affinity.

Competitor visibility scores and ranked keyword lists export as a named competitor group. Each competitor app becomes a tag on a Competitors Audience. The ranked keyword list for each competitor stores as a text merge field or Audience note. Because MobileAction competitor sets are user-curated (not globally exported), we preserve the customer's curated group definition so the competitive framing is not lost even though Mailchimp has no native benchmarking view.

Apple Search Ads campaign structures (campaign name, ad group assignments, goal types) do not have a Mailchimp equivalent because Mailchimp is not an ad management platform. We export campaign names and goal types as Audience tags and store the campaign structure as a written inventory document. The customer's admin uses this document to recreate campaign naming conventions in Mailchimp's email campaign builder if desired.

CPP metadata (screenshot URLs, promotional text, video URLs, associated keywords) export as a reference record linked to the Tracked App. The raw screenshot and video URLs point to MobileAction's infrastructure and may not persist after account cancellation — we flag this and extract the URL references during export. Mailchimp Landing Pages can host the promotional text if the team rebuilds the creative assets, but the CPP metadata itself is reference-only in Mailchimp.

Daily or weekly ranking snapshots per keyword-app-country are high-volume time-series datasets that do not map to any Mailchimp object. Mailchimp's data model is contact-per-row, not metric-per-timestamp. We export this dataset as a structured CSV written to a shared storage location for the customer's records and flag it as a dataset requiring a BI tool (Looker, Databox, or a data warehouse) for ongoing ASO reporting if the team continues to need ranking history.

If the MobileAction account contains any app user contact lists (email addresses associated with app installs or push notification segments), these migrate as Mailchimp Audience members. Email addresses map to the email field, first name and last name to FNAME and LNAME merge fields. We deduplicate against existing Mailchimp members by email address before import and flag any contacts with unsubscribed or bounced status from the source as suppressed imports.

User-level settings including tracked countries, notification preferences, and team member assignments export as a JSON configuration blob. These are not Mailchimp-configurable settings because Mailchimp does not have an ASO settings model. We deliver the configuration blob as a written inventory document so the customer's admin can manually note which countries and notification preferences were active in MobileAction for compliance or audit purposes.