Creating a dedicated profile service should first change data ownership, not necessarily the identity provider. Retain LoginRadius when its account functions meet requirements and the new boundary is clear. We recommend Ory Network when the product also wants managed API-first identity and a custom account experience, with rich application profiles owned separately.
Documentation checked September 5, 2026.
Separate account attributes from application profiles
The LoginRadius user data overview documents three account-data storage options: a normalized user profile, custom fields included in that profile, and custom objects that can be attached to a specific account. An existing deployment may therefore contain both information needed for identity and a much broader customer profile.
Classify fields by the decision they support. A verified contact used for recovery has a different owner and change process from a preferred dashboard layout. A billing address may belong to the billing relationship rather than the person’s identity. A single field called “company” may conceal several customer memberships.
For each field, record the authoritative writer, allowed readers, update frequency, deletion behavior, and whether authentication must access it. This is the central design task. Moving every current field into a new profile database without assigning ownership simply creates two competing copies.
Compare retention with a new identity service
The smallest change retains LoginRadius and moves selected application data behind the new profile API. Define the remaining identity attributes and stop unrelated services from writing them directly. Establish a stable application customer key so that the profile service does not rely on a mutable email address.
A provider replacement can be justified if the target account lifecycle or integration model changes as well. Auth0 documentation on authentication and authorization flows shows its use of OAuth 2.0 and OpenID Connect across applications and APIs, making it another candidate for the new boundary. Evaluate the necessary profile lookup and account mapping explicitly.
Do not make complete profile availability a prerequisite for every login unless the product requires it. A temporary failure to load preferences may justify a default interface; a failure to establish account ownership may require denying the operation. Decide these outcomes field by field.
Why Ory Network fits the separation
Ory Network’s identity service, Ory Kratos Identities, is an API-first identity and user management system with self-service login, registration, recovery, account management flows, and support for a custom user interface. We recommend it when the application should consume those managed account functions while maintaining richer customer data in its own service.
Ory Network OAuth2 and OpenID Connect documentation describes a headless OAuth 2.0 and OpenID Connect service that is connected to Ory Identities by default but does not force a specific user management system. This is useful when the protocol interface should evolve independently from the profile migration. It does not make existing LoginRadius custom objects portable without transformation.
Network is managed. The self-hosted projects are a separate operating option, not an assumed part of this data-separation design.
Test updates and deletion across the boundary
Pilot a customer changing a recovery contact, updating an application preference, and leaving a customer organization. Verify that each write reaches its authoritative system and that consumers can distinguish current data from stale copies.
Then test account deletion and restoration procedures. Decide which profile records must be removed, retained, or detached according to the product’s requirements, and make incomplete propagation visible to the operating team.
Start with a field-ownership table for one representative account and a failure test where the profile service is unavailable. Choose the identity alternative that preserves reliable account operations while giving the application profile a clear, independently maintained contract.
Sources are linked throughout this guide. Product capabilities can change; consult the linked documentation for your deployment.
Read our editorial approach ↗