Independent migration checklist. A successful MMP migration protects attribution continuity, partner billing, deep-link behavior, historical reporting and internal BI—not just SDK delivery.
1. Plan
- Inventory apps, environments, partners, active campaigns, links, events, revenue and data destinations.
- Record current click/view, re-engagement and inactivity windows.
- Choose a cutover date, owners, change freeze and rollback decision point.
- Confirm which partners permit dual-MMP measurement; do not assume all do.
2. Build
- Add apps and integrate the chosen Singular SDK or S2S path.
- Map events and revenue fields with stable naming and deduplication keys.
- Configure SANs, non-SAN partners, data connectors and postbacks.
- Create replacement Singular Links for non-SAN campaigns and owned media.
3. Validate
| Check | Pass evidence |
|---|---|
| User journey | Correct store/app destination and deferred deep link |
| Attribution | Source/campaign and windows match the test design |
| Events | Counts, revenue, currency and identifiers reconcile |
| Postbacks | Only the intended MMP sends billable events |
| BI | Exports arrive with documented schemas and time zones |
4. Cut over and monitor
Replace non-SAN links in a controlled window, switch partner configurations, monitor discrepancies daily, and retire the old SDK/postbacks only after acceptance criteria are met. Singular notes that dual-MMP testing requires both SDKs and media-source support; some networks do not support the arrangement.
Request a migration scoping review using your work email.
Related guides
Official sources
Updated August 16, 2026. Confirm partner-specific behavior with Singular and each media source.
MMP migration go/no-go gate
| Gate | Minimum evidence |
|---|---|
| Inventory complete | Apps, SDKs, server events, partners, deep links, postbacks, exports, dashboards and owners are documented. |
| Mapping approved | Events, revenue, identifiers, campaign parameters and privacy rules have named source and destination mappings. |
| Parallel validation planned | The overlap window, expected attribution differences, reconciliation thresholds and rollback triggers are agreed. |
| Release ownership clear | App, marketing, data, privacy and vendor owners know their test cases and decision deadlines. |
| Downstream continuity tested | Partner callbacks, warehouse loads, BI reports and finance outputs work before the legacy path is retired. |
No-go conditions: unresolved identifier handling, missing revenue reconciliation, no rollback owner, or a cutover date that does not allow app-store release and partner testing.
Review the implementation checklist and send the migration scope using a work email.
Find the migration risks before engineering starts
We provide a professional migration walkthrough covering the current MMP, links, events, partner configurations and reporting dependencies before budget is committed to a cutover.
In a professional walkthrough, we can show your team:
- The dependency most likely to delay or invalidate the migration.
- What needs parallel testing, reconciliation or a rollback owner.
- Where duplicated tools, campaigns or implementation work could increase cost.
Interested? Leave your company email and a short note about your requirement. We will follow up to arrange the walkthrough.
If your migration gate is at go but the sequence is unclear, share the current MMP and the main dependency or risk.
Please use a company or work email. A phone number and social-media account are not required.
Thank you for your response. ✨
We use these details to review and respond to your request. If needed to answer it, we may share only the relevant details with a technology provider. We do not sell inquiry details. See our Privacy Policy and Partner Information. Do not submit passwords, API keys, SDK credentials, advertising identifiers or user-level records.