Skip to main content

Best Practices

Practical tips for getting good results with SimplePerm.

Start with a test profile​

Before migrating production profiles, try it with a test profile or run the process in a sandbox. You'll get a feel for how each wizard step works without any risk to your live configuration.

Migrate one profile at a time initially​

Multi-select supports up to 5 profiles per run once you're comfortable. For your first few migrations though, one profile at a time makes it easier to review results and understand what was created.

Always preview before deploying​

Step 3 shows you exactly what permission sets will be created and what they'll contain. Take a moment to review it -- catching issues here is much easier than cleaning up after deployment.

Use Compare after migration​

After a migration completes, open the Permission Viewer and use Compare to verify the new permission set against the source profile. The side-by-side view covers every permission type, so you can confirm everything transferred correctly.

Keep all permission types selected​

SimplePerm supports 13 permission types. Unless you have a specific reason to exclude one, leave them all selected in Step 2. Otherwise you can end up with gaps where permissions exist on the profile but not on the new permission set.

Handle conflicts carefully​

If a permission set with the same name already exists, the wizard asks you how to handle it in Step 4. Rename is usually safer -- it creates a new permission set with a different name. Overwrite replaces the existing one entirely, and that's permanent. Only choose overwrite when you're sure the existing permission set should be replaced.

Export before and after​

Export your profile's permissions to CSV before running the migration, then export the new permission set after. The two files together give you an audit trail showing exactly what changed.

Check migration history for errors​

If something goes wrong, expand the migration record in the History tab. The logs show what happened at each pipeline step -- profile retrieval, parsing, building, deployment, verification, and user assignment. The step where things failed usually points you straight to the cause.

Permission set naming​

SimplePerm generates permission set names using the format PS_[ProfileName]. If the generated name exceeds Salesforce's 80-character limit or conflicts with an existing permission set, you will be prompted to rename it in Step 4. Keep the name short and descriptive.