Google Groups Migration: Email Not Found in Referential
Resolve user mapping errors during Google Groups migration.
Error Message
Matching member ('email@domain.com') error: Email not found in referential
Problem
During Google Groups migration, the platform encounters a user email address that cannot be matched to a target account. This results in an error message indicating that the email was not found in the referential (mapping table).
Impact
When this error occurs, posts will be created in the target environment using the author's original details from the source system rather than being mapped to the correct target user.
Root Cause
User Mapping Flow
Why This Happens
The error occurs because the user is not present in your mapping list. Without this mapping, the platform cannot match the source email address to the corresponding target email address.
Common Scenarios
- • User was not included in the initial mapping import
- • User's email address changed between mapping creation and migration
- • External users or guests posted in the group
- • User left the organization but still has posts in the group
Solution
Step 1: Add User to Mapping List
- Navigate to Mapping Users in the Cloudiway platform
- Click Add User or import via CSV
- Enter the source email address exactly as shown in the error
- Enter the corresponding target email address
- Click Save
Step 2: Restart Migration
- Return to the Groups migration section
- Select the affected group(s)
- Click Restart Migration
- Monitor the migration status for successful completion
Bulk Updates
Prevention
Best Practices
- ✓ Complete User Export
Export all users from both source and target before migration, including external members.
- ✓ Include External Users
Map external email addresses to a generic account or keep as-is if no target exists.
- ✓ Verify Mapping Before Migration
Run a test migration on a small group to identify any missing mappings early.
- ✓ Account for Former Employees
Include mappings for users who left but have historical posts in groups.
Pre-Migration Checklist
- All active users mapped
- External/guest users identified and mapped
- Former employees mapped
- Test migration completed successfully