Required Migration of Adobe Acrobat Sign to the Adobe Admin Console

This article is applicable for required Adobe Acrobat Sign migrations to the Enterprise Term License Agreement (ETLA) Admin Console.

Overview: 

Adobe is enhancing the way you manage your Acrobat Sign users and licenses, bringing increased productivity to you and your organization. As part of this change, Adobe is migrating your Acrobat Sign subscription to the Adobe Admin Console

Required customer migration journey: Migrating Users to the Adobe Admin Console:

Adobe will initiate your organization’s Acrobat Sign user migration to the Admin Console.

  1. As an Admin of Acrobat Sign, you should have received an email from Adobe informing you that your organization is required to migrate your Acrobat Sign users and licenses to the Admin Console.
  2. Within 60 days from the above-mentioned email, you will receive a second email from Adobe.  This email will include:
    • Your organization’s assigned migration date along with the option to schedule a pre-migration call.
    • Attached you will find a detailed migration plan.  Please review this plan prior to your migration date. 
    • If you are currently using SAML for Acrobat Sign login, or, plan to implement SSO (Single Sign-On) in your Adobe Admin Console for your Acrobat Sign users, please let your migration support agent know.
  3. During the migration, your organization will not be able to use and or access Acrobat Sign.  To avoid any impact to assets and workflows, please do not assign any Acrobat Sign license from your Adobe Admin Console until the migration is complete. This will allow us to map your existing Acrobat Sign production account to your Admin Console.  The expected downtime is less than two business hours to migrate the Acrobat Sign backend to the Admin Console.  Please note that:
    • License redeployment is managed by the customer
    • If you currently use IdP (identity provider) initiated login to access Adobe Acrobat Sign and wish to continue with the same login experience for your users, please refer to Enable SSO when authenticated by IdP.
  4. Once the migration is complete, you will receive a third email from Adobe with details on how to access Acrobat Sign through the Admin Console.  

If you have questions concerning the migration plan, scheduled date and need to re-schedule, or require post-migration support, please respond directly to the migration email.

Useful information:

If you have an active integration with one of our partner integration channels and use the auto-provisioning feature to enable user creation, please refer to Partner integration auto-provisioning.

Frequently asked questions:

Yes.

The expected downtime is less than two business hours to migrate the Acrobat Sign backend to the Admin Console.

No.

The migration activity will not change the Acrobat Sign UI experience for your end-users.

Yes.

Your end-users will see an auto-redirection to the Adobe ID page when they go to secure.adobesign.com/public/login to access their Acrobat Sign account.

An external signer can sign the agreements. However, an internal signer will not be able to sign agreements during the downtime caused by the migration activity.

  • External Signer: A user who is not a part of your Acrobat Sign enterprise account as a user.
  • Internal Sign: A user who is a part of your Acrobat Sign enterprise account.

Yes.

Adobe will migrate all your historical data, including templates, web forms, etc.

Yes.

All workflows historically created will remain attached to your account and can be used after the migration.

For the differences, you may find this guide useful: https://helpx.adobe.com/sign/using/adobesign-migrate-to-aac.html.

If you have auto-provisioning enabled on your current Acrobat Sign enterprise account or plan to implement it in the Adobe Admin Console for your Acrobat Sign users after the migration, there is an additional action for an Acrobat Sign account admin after the migration.

Please refer to this article for the exact steps: https://helpx.adobe.com/sign/using/partner_autoprovision.html.

Note that auto-provisioning will fail to create users if you have user sync enabled on your Adobe Admin Console. Adobe does not have access to create users in your AD, which is in sync with the Adobe Admin Console.

No.

The user groups in the Admin console are not linked to your Acrobat Sign account. User groups in the Admin Console are used only for user deployment, whereas user groups in your Acrobat Sign account are for implementing Acrobat Sign-specific settings.

Adobe is enhancing the way that organizations manage Acrobat Sign users.  All customers will be required to manage users through the Adobe Admin Console.  There will be no changes to the underlying Acrobat Sign service.

Get help faster and easier

New user?