Skip to main content

Data Migration

The LoginRadius Data Migration solution offers flexible and reliable options to transfer your existing customer data to the LoginRadius platform seamlessly. Designed to ensure a smooth transition with zero downtime, our migration tools help you retain business continuity while enhancing your customer experience. We provide multiple convenient methods to suit your specific migration needs.

Types of Migrations

LoginRadius supports multiple data delivery methods to ensure a smooth and efficient migration to our platform. During the initial planning phase, our Data Migration Team will work closely with you to assess your current data structure and recommend the most suitable delivery approach.

Below is a high-level overview of the available data delivery options.

  • Bulk Migration: Your existing customer database is exported in CSV/JSON or another format that aligns with your business requirements. LoginRadius will provide a secure, dedicated SFTP server (or coordinate an alternative transfer method) for uploading the files.
    Our team will configure the migration service to verify, sanitize, and import the data into the LoginRadius Cloud Storage. This method supports comprehensive data normalization, sanitization, and complex transformation logic, ensuring data accuracy, consistency, and a seamless transition with minimal impact on your users.

  • Just in Time Provisioning(JIT): Leverage automated workflows and APIs to automatically provision users in real time from your existing identity provider. This method allows you to migrate users incrementally as they authenticate while preserving all relevant user attributes and claims. JIT is ideal for minimizing migration overhead and ensuring a seamless experience for end users without requiring a bulk data transfer.

Bulk Migration

Our Bulk migration service is configured to verify, sanitize, and transform the data before importing it into the LoginRadius Cloud Storage. This method is ideal for migrating large datasets in a structured and controlled manner with minimal impact on your users.

Key Features of Bulk Migration

  • Extensive support for data normalization, sanitization, and transformation

  • Support for importing existing encrypted passwords (hashes)

  • Full control over field mapping

  • Secure data handling through SFTP or authenticated API access

  • Designed for high-volume, one-time, or staged migrations

Bulk Migration Process

Below is a high-level overview of the standard bulk data migration process with LoginRadius:

Partner IAM

Migration Phases

LoginRadius follows a structured and collaborative approach to ensure a successful data migration experience. Below are the key phases of a typical bulk migration project:

This is the stage where LoginRadius gathers your migration requirements and plans the initial phases of the migration. We will work closely with your team to ensure all migration requirements are understood and the next steps and timelines are established.

Your dedicated LoginRadius Customer Success Manager (CSM) will:

  • Provide a Data Migration package containing a questionnaire to elicit your migration requirements.

Client Responsibilities in this Phase:

  • Review the Data Migration package and return the completed questionnaire
  • Provide a data set of 10-100 test customers. These customers can have either dummy(recommended) or test customer data.

Just-In-Time Provisioning Migration

When migrating users from a legacy identity system, importing all user records at once can be complex, especially if your database includes inactive or outdated accounts. Just-In-Time (JIT) Migration offers a more innovative alternative by provisioning user accounts in LoginRadius only when the user actively log in.

This approach enables incremental migration, ensuring only verified, active users are moved to the new system—without disrupting their experience.

LoginRadius supports JIT migration through two flexible methods:

  • API-Based JIT – Ideal for companies who want full control over the login and provisioning logic via backend APIs.

  • Orchestration-Based JIT – Best for teams using the LoginRadius Identity Orchestration Engine to manage flows with minimal code visually.

Both methods authenticate the user against your existing identity provider if it’s not found in LoginRadius. Upon successful validation, the user is created in the LoginRadius Cloud Directory. From that point forward, LoginRadius became the system of record for authentication.

Key Benefits of JIT Migration

  • No bulk imports required
  • Improves data hygiene by only migrating active users.
  • Supports custom logic for claims, roles, and attributes during migration.
  • Flexible implementation options depending on your infrastructure.

API-Based JIT Migration gives you full control over the authentication and user provisioning flow through your backend. When a user attempts to log in, your backend first checks if the user exists in LoginRadius. If not, it validates the credentials against your legacy identity system, and upon successful authentication, provisions the user in LoginRadius using the appropriate APIs.

This method is ideal for teams that:

  • Prefer building and managing logic in their backend
  • Want fine-grained control over how users are validated and provisioned

It’s highly customizable and suited for developers who are comfortable with API-first implementations.

🚀Get Started with the JIT IO Workflow Using a Preconfigured Template

To explore how the Just-in-Time (JIT) Identity Orchestration workflow operates, you can import our preconfigured JIT IO JSON file. Follow these steps:

  1. Download the sample workflow json file

  2. Go to Orchestration > Workflows in your dashboard.

  3. Click the New Workflow button and upload the downloaded JSON file.

  4. Once the import is successful, you’ll be redirected to the Workflow Builder with a sample JIT migration template.

  5. Add the endpoint for your external identity lookup API in the External Identity Lookup node.

To learn more about Identity Orchestration and how it works, refer to the Identity Orchestration Overview.