Auth Users Migration

Your users are the heart of your application. The Auth Users component migrates all user accounts from one Supabase instance to another, preserving credentials so your users can log in to the new instance without resetting their passwords.

What Gets Migrated

When you select the Auth Users component, Stack2X transfers:

• User accounts -- Every user record in the auth.users table, including email addresses, phone numbers, and user metadata.
• Password hashes -- Encrypted password hashes are copied directly. Users keep their existing passwords and do not need to create new ones.
• OAuth identities -- Linked social login identities (Google, GitHub, etc.) are preserved so users can continue signing in with their preferred provider.
• User metadata -- Both raw_user_meta_data and raw_app_meta_data fields are included.
• Confirmation status -- Email confirmation timestamps and phone verification states are carried over. Users who were already verified stay verified.

Plan Availability

Auth Users migration is available on the Starter plan and above. It is not included in the Free tier.

Tips and Considerations

• User IDs stay the same. Stack2X preserves the original UUIDs for each user. This means any references to user IDs in your database rows, storage policies, or application code will continue to work without changes.
• Pair with Auth Config. For a complete auth migration, consider also selecting the Auth Configuration component. This ensures your auth providers, redirect URLs, and security settings match the source.
• MFA and sessions. Multi-factor authentication enrollments are migrated. However, active sessions are not transferred -- users will need to log in again on the new instance.
• Large user bases. Stack2X handles migrations with hundreds of thousands of users. The transfer runs server-side in batches, so browser timeouts are not a concern.