Migrate from MobileAction to HubSpot

HubSpot Free does not support custom properties on deals or custom objects — campaign data mapping is plan-gated

HubSpot's Free CRM tier allows contacts, companies, and deals but restricts custom properties on Deals and blocks Custom Object creation entirely. MobileAction campaign spend data, impressions, and CPA metrics require Deal-level custom fields — which are only available on Starter ($15/seat/month) and above. If the team is on HubSpot Free, we map campaign data to Company custom properties or defer deal-level metrics to post-migration plan upgrade. We audit the destination plan tier before field mapping to prevent schema-breaking discoveries mid-migration. This is a high-severity gating issue that must be resolved before the migration runs.

MobileAction API rate limits throttle keyword extraction per plan tier — large portfolios require paginated multi-pass extraction

MobileAction's Dashboard API enforces rate limits that vary by plan tier — Lite, Pro, and Enterprise have different requests-per-minute caps. For teams tracking hundreds of keywords per app across multiple app profiles, a single API batch won't complete within the default rate window. We implement paginated extraction with exponential backoff and split large keyword sets across multiple nightly passes. If MobileAction's API returns a 429, the extraction pauses and resumes on the next available window. This adds sequencing time but does not cause data loss — we log checkpoint positions so extraction resumes from the last successful page. Teams on higher plan tiers with higher rate limits face shorter extraction windows.

Daily keyword ranking snapshots create record-volume inflation — HubSpot's per-contact and per-object storage economics differ from MobileAction's aggregated view

MobileAction stores one keyword ranking per app per day, creating a time-series dataset that can reach tens of thousands of records for a portfolio of 50+ apps tracked over 12 months. HubSpot is not a time-series database — storing one HubSpot record per daily keyword snapshot is impractical and would inflate record counts beyond what most HubSpot plans comfortably handle. We aggregate daily snapshots into trend indicators (up/down/stable over the last 30 days) and store the latest rank as a single Tracked Keyword custom object record. Full historical time-series data is preserved as a JSON blob in a Rank_History__c field for audit reference, not for reporting use.

MobileAction automation rules have no structural equivalent in HubSpot workflows — rebuilding requires translating alert logic manually

MobileAction automation rules (rank-drop alerts, CPA threshold triggers, keyword opportunity notifications) are built inside MobileAction's own rule engine with conditions specific to ASO data — rank change magnitude, difficulty score thresholds, competitor rank crossings. HubSpot workflows are contact-based and trigger on property changes, form submissions, list membership, and deal stage transitions. There is no one-click translation path. We export each MobileAction automation rule definition as a structured JSON file with its condition logic and threshold values. A HubSpot admin then rebuilds equivalent logic in HubSpot Workflows or Operations Hub, referencing the exported specification. Alert email routing must be reconstructed inside HubSpot's internal notification system or via a connected tool like Slack.

HubSpot's contact-role model for campaign association requires decision before migration — campaign contacts may need re-linkage

HubSpot associates contacts to deals via Deal-ID on the deal record and via Contact ID on the deal's contact roles. If MobileAction tracks which user contacts are tied to specific campaigns (e.g., the user acquisition manager responsible for a campaign), that association requires mapping to HubSpot Deal Contact Roles. Without a native campaign-contact link in HubSpot Free/Starter, we store the association as a custom property on the Contact record pointing to the campaign deal name. Teams on HubSpot Professional and above can use the built-in Deal Contact Role object for a cleaner association model. We surface this as a pre-migration decision point to avoid post-migration data gaps.