User Not in Directory

Root cause: The user does not exist in Active Directory (AD). For any orgs with SSO that have the AD sync enabled, user creation is allowed only through Identity Provider (IdP). As such, the user couldn’t be added through Admin Console during user migration.

Resolutions:

If the user needs to be migrated - The user must be added to the Active Directory with proper permissions by a system administrator. Marketo Engage admin to then rerun the user migration for this user from the Migration Console.

If the user does not need to be migrated - Marketo Engage admin to skip the user in the Migration Console. The “Migration Complete” button appears when all users are accounted for by migrating or skipping. Click the button to conclude the user migration process.

Inactive User

Root cause: AD Sync is enabled, and the user’s federated account exists but in inactive/disabled status.

Resolutions:

If the user needs to be migrated - The user’s status and proper permissions must be restored by a system administrator. Marketo Engage admin to then rerun the user migration for this user from the Migration Console.

If the user does not need to be migrated - Marketo Engage admin to skip the user in the Migration Console. The “Migration Complete” button appears when all users are accounted for by migrating or skipping. Click the button to conclude the user migration process.

Invalid Domain

Root cause: Domain enforcement is enabled in the Admin Console. However, the domain of the email address for the user is not one of the allowed domains, or the domain has been claimed in another org/Admin Console.

Resolutions:

If the user needs to be migrated (and the domain enforcement is enabled in the migrating org) - The email address must be updated in Marketo Engage to comply with the Domain Enforcement (DE) policy. Alternatively, the System Admin can either move the domain to another Domain Enforcement (DE) disabled directory, or create a new directory that isn’t under DE policy. Marketo Engage admin to then rerun the user migration for this user from the Migration Console.

If the user needs to be migrated (and the domain enforcement is enabled in another org) - a system administrator of the org where the domain has been claimed needs to add the user’s email address to the exception list. Marketo Engage admin to then rerun the user migration for this user from the Migration Console.

If the user does not need to be migrated - Marketo Engage admin to skip the user in the Migration Console. The “Migration Complete” button appears when all users are accounted for by migrating or skipping. Click the button to conclude the user migration process.

User Creation Failed

See below

Type2E Failure

See below

Marketo Entitlement Failed

See below

Pendo Migration Failed

See below

User Data Migration Failed

See below

Product Data Sync Failed

See below

Adobe Entitlement Failed

See below

User Sign Out Failed

See below

Adobe ID Creation Failed

See below

Failed

Root cause: These errors can be caused by various reasons in the backend.

Resolutions:

Submit a support case with relevant details for Marketo Support.

Previous pageMarketo Engage Support Migration
Next pageBulk Export API Information

Marketo Engage