---
schema_version: "1"
id: aca7dd57f1d0d40ed79c730e7aeb871585efbeb3865bc6e3d171bcf1ed9a9cf7
title: "Post Migration: What Changes and What Doesn’t?"
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/hr_svc_post_migration_changes_overview.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.hr_svc_post_migration_changes_overview.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: dd73c6f3973ba66fe9b26e17ee00bdce63cddb7b9dfb304529f4272280a1cf89
description: CCP to UEL migration is a foundational shift in how employee users are modeled, focusing on identity transformation.
products:
  - Service Cloud
release: "264"
---
# Post Migration: What Changes and What Doesn’t?

CCP to UEL migration is a foundational shift in how employee users are modeled, focusing on identity transformation.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support-264-0-0-production-enus/dd14551c-a772-4db6-9a1d-d84df8df2980/images/icon_note.png)

Note Customizations such as Apex triggers, Apex classes, and custom flows are not automatically migrated or updated. After the migration is successful, test and reconfigure these components to ensure they function as expected.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small " summary="What Changes and What Doesn’t?">
      <caption>What Changes and What Doesn’t?</caption>
      <colgroup>
        <col style="width:50%">
        <col style="width:50%">
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d102283e42">What Changes?</th>
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d102283e45">What Stays the Same?</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="What Changes?" class="slds-cell-wrap" style="vertical-align:top;" headers="d102283e42 "><strong>Target Profile: </strong>During migration, the target user profile is mapped to the
            Unified Employee profile. After the migration is successful, verify that the correct
            profile is assigned to your users and reconfigure any profile-based settings as
            required.</td>

          <td data-label="What Stays the Same?" class="slds-cell-wrap" style="vertical-align:top;" headers="d102283e45 "><strong>Permission Sets &amp; Permission Set Groups: </strong>Permission sets and
            permission set groups don’t change during migration. However, after the migration is
            successful, you need to <a href="https://docs.google.com/document/d/1uOVHnyhAWsWwgEbMx3xu_eXMB-K5tB0FxCdL74h-C0Y/edit?tab=t.0#bookmark=id.ookp4qkqoft3" target="_blank"><u>set up user access policies for UEL
                migration</u></a>.</td>

        </tr>
        <tr class="">
          <td data-label="What Changes?" class="slds-cell-wrap" style="vertical-align:top;" headers="d102283e42 "><strong>Sharing Sets: </strong>Sharing sets aren’t applicable to UEL. Post migration, use
            Apex or Sharing Rules instead. </td>

          <td data-label="What Stays the Same?" class="slds-cell-wrap" rowspan="2" style="vertical-align:top;" headers="d102283e45 "><strong>Role</strong>: Existing role assignments and reporting structure are
            preserved during migration.</td>

        </tr>
        <tr class="">
          <td data-label="What Changes?" class="slds-cell-wrap" style="vertical-align:top;" headers="d102283e42 "><strong>User License: </strong>All existing CCP license users are migrated to UEL. All new
            users use UEL by default. </td>

        </tr>
      </tbody>
    </table>