Step 4: Resolve Conflicts
This step only appears when a permission set with the same API name already exists in your org. No conflicts? The wizard skips straight to the run step.
Why Conflicts Happen
SimplePerm generates the permission set API name from the source profile name. If you've already migrated the same profile before, or a permission set with that name was created some other way, the names collide.
Your Three Options
For each conflicting profile, you can choose how to handle it:
Skip
Don't create a permission set for this profile. The migration proceeds for any other selected profiles that don't have conflicts, but this one is left out.
Use this when the existing permission set is already correct.
Rename
Enter a new API name. SimplePerm creates the permission set under that name instead of the default.
Good for keeping the existing permission set and creating a second one alongside it -- for example, Standard_User_v2.
Overwrite
Replace the existing permission set with the newly generated one. The old permission set is updated with permissions from the current migration.
Overwrite permanently replaces the existing permission set. Any manual customizations on it will be lost.
Resolving Multiple Conflicts
If multiple profiles have conflicts, you'll see a resolution option for each. You can mix strategies -- skip one, rename another, overwrite a third.
Moving Forward
Once all conflicts are resolved, click Next.