Skip to main content

Step 6: View Results

Here's what you see once the migration finishes.

Reading the Results​

Each profile shows one of three statuses:

  • Success -- Permission set created, all selected permission types deployed without issues.
  • Partial Success -- Permission set created, but some types had problems. The permission set exists with whatever types did deploy correctly.
  • Failed -- Permission set could not be created. Nothing was deployed for this profile.

You'll also see counts: how many permission sets succeeded and how many hit errors.

Digging Into Details​

Click any profile row to expand it and see per-type results.

Failed types show an admin-friendly error message. SimplePerm translates raw Metadata API errors into plain language -- so instead of a cryptic FIELD_INTEGRITY_EXCEPTION, you'll see something like "Permission set name exceeds the maximum length" or "Referenced Apex class not found."

tip

Partial Success means the permission set exists with the types that worked. Fix the underlying issue and run a new migration for just the failed types.

Common Error Scenarios​

A few things that can cause errors:

  • Name too long -- Salesforce has a character limit on permission set API names. If the generated name exceeds it, deployment fails.
  • Referenced item not found -- The profile references an Apex class, Visualforce page, or flow that no longer exists in the org.
  • Metadata API limits -- Very large profiles can occasionally hit Salesforce's per-transaction metadata limits.

Most errors are straightforward. Fix the issue and re-run the migration for the affected profile.

Moving Forward​

If at least one permission set was created, the next step lets you assign it to users. If everything failed, close the wizard, fix the errors, and try again.

Step 7: Assign Users →