Analytics User Migration to the Admin Console
What you need to know about the Analytics user ID migration to the Admin Console in the Adobe Experience Cloud.
For general help on Admin Console topics (not related to the Analytics migration), see Admin Console User Guide .
After you migrate, you can manage Experience Cloud users and products in the Admin Console.
What is the Analytics user ID migration?
The Analytics user ID migration enables administrators to easily migrate user accounts in Analytics User Management to the Adobe Admin Console. After your users are migrated, they will have access to the solutions and core services available in the Experience Cloud. The migration is being rolled out to customers in phases.
The benefits of using the Admin Console include:
Analytics users can sign in to the Experience Cloud and all solutions using their Adobe ID or Enterprise ID. This sign-in enables access to integrated solutions and core services in the Experience Cloud.
After the migration, users who attempt to sign in via legacy logins ( my.omniture.com and sc.omniture.com ) are redirected to experiencecloud.adobe.com .
Manage user identity and permissions
Analytics administrators can manage users and permissions exclusively in the Admin Console (http://adminconsole.adobe.com/enterprise/).
Manage products and core services
What to know (and do) before migrating user IDs (FAQ)
Answers to questions you might have before the migration.
|Question / Task||Answer|
I am an Analytics administrator and received a pre-migration email. What do I do first?
Verify that you have an Adobe ID and can access the Experience Cloud Admin Console .
If not, contact Adobe Customer Care . (You should first contact your system or product administrator who can invite you to the proper organization.)
AEM integrations with Analytics
AEM users with an integration to Analytics will need to change their configuration to use the Analytics shared secret instead of the password.
You should do this before the migration is enabled. Once the migration is disabled, the originally configured password will no longer be valid.
To obtain the shared secret in Analytics
The shared secret can be obtained from Analytics ( Analytics > User Management ) and is different for each user.
To update your AEM configuration with the shared secret
Update Report Builder
Important: Update your installation of Report Builder to the latest version.
When does the migration begin?
Adobe will notify Analytics administrators via email with instructions about when the migration will begin.
Migrations to the Admin Console will occur in waves. On the day of migration, Adobe notifies Analytics administrators and grants them access to the migration tool. After a login company meets the criteria defined for each migration wave, Adobe will:
On the day of the migration, your former permission groups are automatically copied to the Admin Console. You will no longer be able to invite new users or create new groups in Analytics Admin Tools.
After the migration:
What will happen on the start date of the migration?
At 10:00 a.m. UTC on the start date of the migration:
How do I migrate user IDs?
Click Migrate User IDs on the Admin page, under User Management. Use the tool to add users to product profiles in the Admin Console (replicated from permission groups in Analytics). You can migrate user IDs at your own pace.
Administration privileges are required. Once the migration is complete, it cannot be reversed.
On the end date of the migration, my.omniture.com access will be disabled for users within their login company. Users (including those that are yet to be migrated) will be redirected to login via the new Experience Cloud URL ( experiencecloud.adobe.com )
Note: Adobe recommends taking the opportunity to perform an audit of your users and groups before migrating. Delete old and unused accounts, or accounts that should no longer have access to the product (such as employees no longer with the organization).
Related topic: Migrate Analytics user accounts for Enterprise and Federated IDs .
Will the migration affect my Analytics implementation or how data is collected?
The migration tool exists to help you transition user IDs and permissions from Analytics User Management to the Experience Cloud Admin Console .
How long does the migration process take?
All current Analytics administrators will receive a pre-migration notification email four weeks prior to the migration. (The actual start date will appear in the Analytics interface.)
When the migration begins, administrators will have 60 days to complete the process.
Can I expedite my migration?
Yes. However, Adobe recommends that you use the time before the migration begins to:
To expedite your migration, contact your Customer Success Manager at Adobe Customer Care and submit a request for an earlier start date.
I am an Analytics administrator without access to the Admin Console. Who can help me gain access to the Admin Console?
Any system or product administrator that has access to your organization's Admin Console can give you access. If you are not sure who within your organization has administrator privileges in the console, contact Adobe Customer Care .
Can I postpone the migration start date?
Yes. Contact Adobe Customer Care .
See below for a description of the changes to your current Analytics User and Permissions management on the start date.
Now that my company is migrating to the Admin Console, where do I create new users and permission groups before the start date of the migration?
Before your migration start date, you can create users in the Admin Console or in Analytics > User Management.
After migration begins, you can create users and permission groups only in the Admin Console.
see the Migration section below for more details on what happens on the start date of the migration.
When can I implement single sign-on using Federated IDs?
A tool will be available soon in the Admin Console that enables you to change ID types from Adobe IDs to Federated IDs. During the migration, you cannot migrate users as Federated IDs.
What to know during the migration (FAQ)
Important information about the migration process and how it impacts current user management.
How are permission groups replicated to the Admin Console? What about my users?
A migrated Analytics group is a called a Product Profile in the Admin Console. Permission settings for the original group are retained in the migration. However, the users assigned to the group are not migrated. When a user belonging to that group is migrated using the migration tool, that user is assigned to that product profile.
For example, a West Coast Operations permission group that entitled its members to Report Builder and Analysis Workspace (with certain report suites, metrics, dimensions) will become a West Coast Operations product profile.
Can I delegate the migration effort to another administrator?
Once your migration begins, any administrator that accesses your Analytics instance via the Experience Cloud can use the migration tool to begin (or continue) migrating users.
Can I update permission group membership for un-migrated users?
Yes. You can change the group membership of un-migrated users from within the Analytics User Management section.
Awaiting clarification from Ashok about where that's done.
Can I create users and permission groups in Analytics after my migration begins, and then use the migration tool to move them to the Admin Console?
No. Once migration begins, all new users and permission groups (called Product Profiles in the Admin Console) must be created in the Admin Console.
Would users I migrate using the migration tool be assigned the same permissions they had in Analytics?
Yes. Users migrated using the tool will be accorded the permissions they currently have in Analytics. Furthermore, they will retain access to their Analytics assets (like segments, projects, calculated metrics, and so on) when they access Analytics via the Experience Cloud.
Do users I migrate to the Admin Console continue to have access to Analytics using my.omniture.com ?
Yes. Migrated users will continue to be able to access Analytics using their existing user name and password via my.omniture.com until the end date of the migration, unless you disable their legacy login access via the migration tool.
Two or more of my users have the same email ID in their Analytics record. What happens if I migrate them?
Because user accounts in the Admin Console require unique email IDs, you will run into a "Duplicate Email ID" error when you try migrating more than one of these users. You can update the email IDs of un-migrated users under the User Management (legacy) section before you retry the migration.
What do I do after migrating my users?
Disable their legacy login access to my.omniture.com . You will not be able to turn off legacy login unless they have been migrated.
Can I track the migration process?
The migration tool includes a dashboard that displays how many of your users have been successfully migrated, and how many of them have their legacy login disabled.
Ideally, you will have successfully migrated your login company to the Admin Console when a 100% of your users have completed migration and have had their legacy logins disabled.
I need to perform user and permission management during the migration. Which tool can I use to perform this task?
After the migration begins, you will use the Admin Console to create and manage new users and product profiles.
What do my users experience when I migrate them using the tool?
They will receive a welcome email addressed to the email ID in their Analytics user record, notifying them about their new way to access Analytics via the Experience Cloud. If they do not have an existing Adobe ID, they will be prompted to create one, after which they can access the solution using their Adobe ID.
Can I use APIs to migrate my users instead of using the migration tool?
No. You must use the migration tool to ensure all your existing users are migrated to the Admin Console.
What Analytics user-management features are not available in the Admin Console?
These will remain available to you in Analytics user management.
See Unsupported Analytics features in the Admin Console for more information.
We created several configurations in the Admin Console and mapped them to Analytics permission groups. What will happen to those configurations when the migration begins?
Analytics permission groups are recreated in the Admin Console as product profiles, just like all your other groups. This means you will see two product profiles in the console that essentially have duplicate permissions. You can delete duplicate product profiles from the Admin Console.
What is my next step after migrating user?
Once you have migrated the user or a set of users, your next step is to disable their legacy login via my.omniture.com . You can do that by selecting these users in the migration tool and clicking on the contextual "Disable Legacy Login" option that appears at the top of the screen. Note that this option is only visible when you select a user or set of users that have all been migrated successfully to the Admin Console.
What happens on the migration end date?
After the migration end date (60 days from the start of the migration), all users within your login company are redirected to login via the Experience Cloud login page using their Adobe IDs.
I haven't been able to migrate all my users by the migration-end date. Would un-migrated users lose their access to Analytics?
Users that have not been migrated by the end date will be redirected to the Experience Cloud login page (experiencecloud.adobe.com) and will be unable to access Analytics. However, you will continue to have access to the migration tool so you can find and migrate them to restore their access.
What to know after the migration (FAQ)
|Question / Issue||Answers|
Deleting users from the Admin Console
In Analytics, a deleted user is set as expired , but the account continues to exist. Preserving the account enables the transferring assets, such as segments, calculated metrics, scheduled reports, projects, and so on.
You can manually set an account expiration date in Analytics in Admin Tools. Once the expiration date is met, the user will not be able to access Analytics, but their actual Experience Cloud user account (e.g. Adobe ID, Enterprise ID, Federated ID, etc.) doesn't expire. They can still log into Experience Cloud, they just won't be able to click into Analytics.
Unsupported Analytics features in the Admin Console
Review the following issues that may apply to you during the migration.
|Question / Issue||Answers|
Admins migrating to the Admin Console will no longer be able to use the "Log-In As" function to access non-Admin user accounts that have been migrated to the Admin Console. This feature is being deprecated from Analytics.
User expiration and asset transfer
The Admin Console does not support user expiration or asset transfer. Admins will use the Analytics Users and Assets section under Admin Tools in Analytics for both functions.
Last Access (Last Login)
Details around a users' last-login date and time will be available in the Analytics Users and Assets link and not the Admin Console. The last-login date in Analytics is specific to when users actually accessed Analytics from within Experience Cloud and does not reflect the date/time when they logged into the Experience Cloud.
User Management APIs Adobe-supported identity types
Admins migrating to the Admin Console should configure user management APIs offered at Adobe I/O for programmatic access to user accounts in the Admin Console.
The Analytics Permission APIs will be turned off when you are enabled for the migration.
Web Service Credentials
Users' web-service credentials (and their shared secret) will not be available in the Admin Console and can be accessed by clicking into the specific user from the Analytics Users and Assets section.
Analytics single sign-on configurations will be removed when you have completed the migration. They will remain active during the migration. Customers that use Analytics single sign-on should upgrade to Adobe Federated ID .
Analytics recommends that you migrate your users as Adobe IDs first to easily create the Experience Cloud accounts, and then convert those accounts to Federated single-sign users.
Downloading permission groups
Downloading of Permission Group information will no longer be supported in either the Analytics Admin Tools or the Adobe Admin Console. Customers should use the adobe.io user management APIs to get permission group information in bulk.
Account Creation Date
Account Creation Date information is no longer supported in either the Analytics Admin Tools or the Adobe Admin Console.
Bulk email to users will no longer be supported in either the Analytics Admin Console or the Adobe Admin Console. Customers can bulk export their users' email addresses from Adobe Admin Console and send an email using any email client they wish.
How to notify your users about the migration
You may want to pro-actively communicate this migration plan to your current users. Here is a template you can customize to send all your current Analytics users:
To email all users, navigate to Analytics > Admin > User Management > Email Users .
Subject: Coming Soon - A new way to login to Adobe Analytics and Adobe Experience Cloud.
Body: Hello Adobe Analytics users!
Our company will begin migrating all Adobe Analytics accounts away from https://my.omniture.com/login/ to Adobe Experience Cloud ( experiencecloud.adobe.com ). With this migration, your Adobe Analytics account will be upgraded to enable access to Analytics via the Adobe Experience Cloud. While the method to access Analytics will change, all your existing permissions to your report suites and tools will be preserved.
Next steps: We will begin to migrate users beginning on INSERT DATE . Watch for a welcome message with your new login addressed to the email id listed under your analytics account. If you have not setup an Adobe ID linked to your email address, you will be asked to setup an account .
Please contact your Analytics administrators if you have any questions or concerns.