Hybrid

Summary

Hybrid migration combines multiple strategies to optimize for different user segments. The most common approach is using JIT migration for active users (who log in regularly) and bulk password reset for dormant users (who haven't logged in recently). This gives you the best of both worlds: great UX for active users and a predictable path for inactive accounts.

When to Use

This strategy works best when:

  • You have a mixed user base with both active and dormant users
  • You want to optimize UX for active users while handling inactive accounts
  • You can segment users by activity level
  • You want to minimize disruption for your most important users
  • You have the technical capability to run multiple strategies in parallel

Pros

  • Best UX for active users (JIT migration)
  • Predictable handling of dormant users (bulk reset)
  • Flexible - can adjust strategy per user segment
  • Reduces overall migration risk
  • Can optimize for different user cohorts

Cons

  • More complex to implement and operate
  • Requires user segmentation logic
  • Need to coordinate multiple migration paths
  • More moving parts to monitor
  • Requires understanding of user activity patterns

Typical Flow

  1. 1Segment users by activity level (e.g., last login date)
  2. 2For active users: Set up JIT migration proxy
  3. 3For dormant users: Export and import into new provider
  4. 4Send password reset emails to dormant users
  5. 5Update application to use new provider
  6. 6Active users migrate on first login (JIT)
  7. 7Dormant users reset passwords when they return
  8. 8Monitor both migration paths
User Activity Buckets: Use user activity data to decide which strategy to apply. Common segmentation: active (logged in within 30 days), semi-active (30-90 days), dormant (90+ days). Adjust thresholds based on your user base.

Social Logins Considerations

Social logins need to be handled differently for each strategy:

  • JIT path: Handle social login linking as users log in (see JIT migration guide)
  • Bulk reset path: Include instructions for re-linking social accounts in reset emails
  • Mixed scenarios: Some users may have both email and social logins - plan for account merging

Password Continuity / Reset Expectations

Hybrid approach provides different experiences:

  • Active users (JIT): Keep existing passwords, migrate on first login
  • Dormant users (bulk reset): Need to reset passwords when they return
  • Edge cases: Users who were dormant but become active before bulk reset - handle gracefully

Operational Checklist

Before Migration

  • Analyze user activity patterns to define segments
  • Set up JIT migration proxy for active users
  • Prepare bulk reset process for dormant users
  • Plan communication for each user segment
  • Test both migration paths independently
  • Set up monitoring for both strategies

During Migration

  • Export and import dormant users
  • Send reset emails to dormant users
  • Activate JIT migration for active users
  • Update application configuration
  • Monitor both migration paths
  • Handle edge cases (e.g., dormant user becomes active)

After Migration

  • Track migration completion for both paths
  • Monitor dormant users who return and need to reset
  • Verify all user segments are handled
  • Decommission old provider after grace period

Common Pitfalls

  • Poor segmentation: Wrong activity thresholds lead to suboptimal strategy assignment. Analyze your user base carefully.
  • Coordination issues: Both strategies running simultaneously can conflict. Plan carefully.
  • Edge case handling: Users who move between segments need special handling. Plan for these scenarios.
  • Complexity overload: Hybrid adds complexity. Make sure the benefits justify it for your use case.
  • Monitoring gaps: Need to track both paths. Set up comprehensive monitoring.