> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/integrations/crm/migrating-from-legacy.md). # Migrating from the legacy CRM integration Mobly is replacing its older direct-auth CRM integrations with a **new integration platform** — unified, vendor-neutral, and the home for everything new. If you're still on the legacy integration, you should plan to migrate. New features (Reconciliation, the unified Mapping editor, multi-object syncing, the Qualifiers tab, per-campaign sync) 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 CRM 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 CRM destination is configured in one place per object (Lead, Contact, Company), with **Set Defaults** to pre-populate Mobly's recommendations. Legacy used separate per-object panels and per-CRM 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. * **Better error categorization** — sync errors are grouped by root cause, with deep links from the product directly to the right help section. * **Faster troubleshooting** — when an issue does come up, Mobly support and engineering can debug the new platform faster than the legacy stack. (One reason every "something's broken" call ends with "let's get you on the new platform.") The legacy 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: 1. **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 — typically a Friday afternoon or between events works well. 2. **Mobly flips the switch.** Your **Integrations** page now shows the new UI instead of the legacy interface. 3. **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. ## What carries over and what doesn't **Carries over:** * Leads already in your CRM stay there — the new platform doesn't touch existing records on the CRM side * Your CRM account itself (you'll re-authenticate, but no need to set up a new CRM user) * Mobly's lead history (every lead Mobly has captured is preserved) * Field, qualifier, and campaign mappings - **if you accept the migration prompt during setup setup** (see below) **Needs to be redone in the new platform:** * **CRM authentication** — re-authorize through the new Connect tab * **Sync mode** — defaults to Automatic; switch to Manual on the Connect tab if needed ## Reconfiguration steps after the switch 1. Go to **Integrations** in the left nav. Confirm you see the new card-based layout (CRM, Marketing Automation, etc. as category sections). 2. Click your CRM card. 3. Click **Connect** and authorize through your CRM's login flow. 4. Work through the **two-step setup** dialog that appears — **the order matters, and legacy customers handle step 1 differently than new customers.** See below. 5. Check **Mapping**, **Qualifiers**, and **Campaigns** to confirm your migrated mappings look right. 6. Set your sync mode on the **Connect** tab (Automatic is the default). #### The two-step setup dialog After you authorize, Mobly walks you through two prompts in this order: **Step 1 of 2 — Create Custom Fields.** Mobly asks whether it should automatically create the fields it needs in your CRM account. > **Migrating from legacy? Choose No.** These fields already exist in your CRM — the legacy integration created them when you first set it up. Saying Yes risks duplicate fields that your migrated mappings won't point at. This prompt is intended for organizations connecting a CRM to Mobly for the first time. **Step 2 of 2 — Migrate Existing Mappings.** Mobly reports that it found existing field, tag, and campaign mappings from your previous CRM connection and asks whether to bring them into the new platform. > **Migrating from legacy? Choose Yes, Migrate.** This is the step that saves you the manual rebuild. Your legacy field mappings, qualifier (tag) mappings, and campaign mappings all come across. If you choose **No** here, nothing is lost on the CRM side — you'll just be starting from an empty mapping configuration and building it by hand. Use **Set Defaults** on the Mapping tab for a faster start if you go that route. #### Verifying migrated mappings Migration brings your mappings across, but it's worth a quick pass before your next event: * **Mapping tab** — spot-check that each Mobly field points at the CRM field you expect, per object (Lead, Contact, Company). Anything the legacy integration mapped to a field that no longer exists in your CRM will come across unmapped. * **Qualifiers tab** — confirm your qualifier values landed on the right CRM destinations. * **Campaigns tab** — if you sync per-event campaigns, confirm the campaign associations carried over. Changes on these tabs auto-save as you make them. ## 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 CRM 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. ## What about Marketing Automation? Slack? Other connections? This article focuses on CRM migration since that's where most legacy integrations live. If you also have Marketing Automation or other connections set up, your CSM will sequence the migration for each one. The reconfiguration pattern is the same across all categories. ## Related articles * [Connecting your CRM](/help-center/integrations/crm/connecting.md) * [Sync modes](/help-center/integrations/crm/sync-modes.md) * [Reconciliation](/help-center/integrations/crm/reconciliation.md) * [CRM Integrations](/help-center/integrations/crm.md)