Migrating from the legacy MA integration
Mobly is replacing its older direct-auth Marketing Automation integrations with a new integration platform — unified, vendor-neutral, and the home for everything new. If you're still on the legacy MA integration, you should plan to migrate. New features (Reconciliation, the unified Mapping editor, the Qualifiers tab, per-Program sync for Marketo) only ship to the new platform, and any new sync error handling lands there too.
Why migrate
The new platform gives you:
Reconciliation tab — see exactly which leads didn't sync to your MA tool and why, with self-serve fixes for most error categories. The legacy integration didn't surface sync errors with this clarity.
Unified mapping UI — every Mobly field's destination is configured in one place per object, with Set Defaults to pre-populate Mobly's recommendations. Legacy used separate per-vendor auth screens.
Auto-save mappings — changes save immediately as you make them. The legacy integration could lose mappings if you switched tabs before saving.
Sync modes — toggle between Automatic and Manual sync per integration. Legacy didn't expose this.
Faster troubleshooting — when an issue does come up, Mobly support and engineering can debug the new platform faster than the legacy stack.
The legacy MA integration is in maintenance-only mode — no new features, security and compliance fixes only.
How migration works
You can't flip yourself to the new platform — it's a toggle on Mobly's side, per organization. To migrate:
Ask your CSM to enable the new integration platform for your org. This is fast (a config change). Schedule it for a low-traffic window if you're worried about disruption.
Mobly flips the switch. Your Integrations page now shows the new UI instead of the legacy interface.
You reconnect and reconfigure — see the steps below.
There's no auto-migration of legacy mappings. The new platform uses a different mapping system, so you'll set up mappings fresh. Plan for ~30 minutes of reconfiguration if you have a complex setup, less if your mappings are straightforward.
Vendor-specific legacy pain points
Marketo: The legacy integration required setting up a LaunchPoint service, a custom REST role, and copying Client ID/Secret into Mobly. The new platform uses standard Marketo OAuth — none of that LaunchPoint configuration is needed.
Pardot: The legacy integration used Pardot username + password + Client ID. The new platform uses Salesforce SSO (since Pardot is a Salesforce-owned product), so the connecting user authenticates through Salesforce instead.
What carries over and what doesn't
Carries over:
Leads already in your MA tool stay there — the new platform doesn't touch existing records on the vendor side
Your vendor account itself (you'll re-authenticate, but no need to set up a new user)
Mobly's lead history (every lead Mobly has captured is preserved)
Needs to be redone in the new platform:
Authentication — re-authorize through the new Connect tab
Field mappings — set up under the Mapping tab (use Set Defaults for a fast start)
Qualifier mappings — set up under the Qualifiers tab
Program mappings (Marketo only) — set up under the Campaigns tab if you sync per-event Programs
Sync mode — defaults to Automatic; switch to Manual on the Connect tab if needed
Reconfiguration steps after the switch
Go to Integrations in the left nav. Confirm you see the new card-based layout with categories (CRM, Marketing Automation, etc.).
Click your MA tool card under the Marketing Automation section.
Follow the Connecting a Marketing Automation tool steps — connect, then work through Mapping → Tags → Campaigns → Sync mode.
Capture a test lead at a test event and confirm it lands in Reconciliation → Cleared.
Once you're confident, you're done. The legacy code path is no longer used for your org.
What if I don't migrate?
The legacy integration keeps working until Mobly fully sunsets it. Mobly will give advance notice before the cutoff. Once retired, organizations still on legacy lose access to MA sync entirely until they migrate.
You also miss every feature that's only on the new platform — the most painful of which is Reconciliation. Without it, sync errors just fail silently and your CSM has to dig into logs to figure out why a lead didn't make it.
Related articles
Last updated
Was this helpful?