Migration › Knowledge Base › The Profile lock
The Profile lock
Think of the schema like wet concrete. While it's wet you can shape it freely. Enable Profile and you've let it set, beautiful if the shape is right, a jackhammer job if it isn't.
The Profile toggle makes a schema eligible for Real-Time Customer Profile, the unified, cross-source profile that powers RT-CDP and AJO. The moment a Profile-enabled schema ingests data, it locks: you can't remove fields or disable Profile without resetting the entire sandbox.
An Analytics-only migration does not need Profile at all. CJA-readiness comes from clean XDM, not from this toggle, so there is no reason to flip it during the build.
For your migration: leave Profile OFF. Build the cleanest XDM you can, validate for weeks, and only enable Profile later, deliberately, when a profile use-case actually arrives. This is the single most common irreversible mistake in the whole project.
Leave Profile OFF during the Analytics migration. Enable it only when a real-time profile use-case genuinely exists, and treat that as its own signed-off decision.
What Profile is
The Profile toggle makes a schema eligible for Real-Time Customer Profile, Adobe's unified, cross-source view of a person that powers Real-Time CDP and Journey Optimizer. It's a genuinely powerful capability, and entirely unnecessary for an Analytics-only migration.
Why it's treated like a live wire
The moment a Profile-enabled schema ingests data, it locks. You can no longer remove fields, change certain field types, or disable Profile, the only way back is resetting the entire sandbox, which discards everything in it. There is no "undo." This is the single most common irreversible mistake in a Web SDK project, usually made by someone flipping the toggle "to see what it does."
When to enable it
| AA only | Leave OFF, never needed. |
| CJA later | Leave OFF, CJA reads clean XDM without Profile. |
| RT-CDP / AJO | Enable later, deliberately, after weeks of validation, when a profile use-case is real. |
The discipline: build the cleanest XDM you can now, validate thoroughly, and treat enabling Profile as its own decision with its own sign-off, not a checkbox you tick during setup.