CCP to UEL Migration FAQs

Review common questions about CCP to UEL migration, including rollback, downtime, inactive users, phased rollout, sandbox testing, error handling, and post-migration license behavior.

• Can the migration be rolled back?

  No. The migration process is intentionally one-directional and irreversible. Once a user's license and UserType are migrated from CCP to UEL, you can’t revert them back. Because of this, it is critical to thoroughly test the process and complete all pre-migration configurations before migrating to UEL.

• What's the impact on employees during downtime?

  Enabling the Unified Employee License migration causes system downtime during which employees cannot log in. To minimize business disruption, administrators should carefully coordinate and schedule a dedicated go-live window. Additionally, after the migration completes, all active user sessions are terminated and the UserInfo cache is cleared. This forces employees to log in again so the system can enforce their updated license and access configurations.

• What happens to inactive users during migration?

  The platform migration utility does not support migrating inactive users from CCP to UEL. The job is specifically designed to transform active identities while preserving their historical metadata.

• Is phased migration possible?

  No. A phased or partial migration is not possible. When you turn on UEL migration, it applies at the organization level. Once enabled, the preference is permanent, which means all new users must use the UEL model, and you can no longer create or add legacy CCP employee users.

• Are users deactivated during the migration process?

  No, users are not deactivated during the migration. The tooling executes an in-place identity transformation that migrates the user type from external (C) to standard internal (S). This process intentionally preserves the UserId, Username, Email, and all associated record ownership or audit trails (such as CreatedById and LastModifiedById) without requiring user deactivation.

• Can the migration tool be used in a Sandbox?

  Yes. We recommend testing the entire migration process in a Sandbox organization before deploying it in production. This allows you to validate your custom profiles, permissions, and sharing rules beforehand.

• What should I do if I run into errors?

  The migration job operates as an asynchronous background process executed in controlled batches of 200 records. If an error occurs, use the following method to troubleshoot:

  • Review Track Migration Status: Administrators have access to a real-time tracking interface and a dedicated list view showing all employees that failed during the run, including their employee IDs.
  • Identify the Stage of Failure: The underlying logic is divided into stages (for example, removing permission sets, direct DB updates, group reassignments). The interface displays detailed failure reasons pinpointing the exact step where the process stalled.
  • Correct and Retry: Once the underlying operational or data issue is resolved, administrators can use built-in mechanisms to retry the failed records. The retry mechanism automatically resumes from the specific point of failure rather than restarting the entire workflow. Each attempt creates an audited version history for easy tracking.
• What happens to my CCP licenses post migration?

  It depends on how the license is being used: For Employee Profiles:

  • Cancel all CCP licenses assigned to employee profiles once the migration is complete. These will not deactivate automatically.
  • For Other Use Cases: No action is required. All other CCP licenses will continue to function normally without interruption.
• Why do Unified Employee Users fail to authenticate with Slack or access Agentforce Agents for Slack?

  Enable the API Enabled system permission for the Unified Employee User profile for Slack authentication and Agentforce Agent access for Slack to work.

  To enable this permission, choose one of the following approaches:

  • Clone the standard profile: Clone the Unified Employee User standard profile and manually enable the API Enabled permission on the cloned profile.
  • Create a Permission Set: Create a permission set with API Enabled enabled and assign it to Unified Employee Users.