Skip to main content

Troubleshooting

Common issues and how to fix them.

"Insufficient Privileges" error when opening SimplePerm​

Cause: Your user does not have the SimplePerm_Admin permission set assigned.

Fix: Go to Setup > Permission Sets > SimplePerm_Admin > Manage Assignments and add your user. This permission set is required to access the SimplePerm app.

Migration fails with "FIELD_INTEGRITY_EXCEPTION"​

Cause: The generated permission set name is too long (Salesforce has an 80-character limit) or contains invalid characters.

Fix: In Step 4 (Conflict Handling), use Rename to choose a shorter, valid name. Stick to letters, numbers, and underscores.

"Unable to connect to Metadata API" error​

Cause: API access is not enabled for your Salesforce edition, or there's a connectivity issue.

Fix: Confirm your org has API access. Enterprise, Unlimited, and Developer editions include it by default. Professional Edition requires an API add-on. If your edition should support it and you're still seeing this error, check with your Salesforce administrator -- API access may be restricted at the profile level.

Migration shows "Partial Success"​

Cause: Some permission types were migrated successfully, but others encountered issues during deployment.

Fix: Open the History tab and expand the migration record. Look for Warning or Error log entries -- they'll tell you which permission types had problems and why. Common causes: references to objects, fields, or Apex classes that don't exist in the target org.

Permission set is missing some permissions after migration​

Cause: Certain profile settings cannot be migrated to permission sets because they are profile-only features.

Fix: Use the Permission Viewer's Compare feature to see the source profile and new permission set side by side. Check whether the missing items are among the three non-migratable settings:

  • Login Hours -- Profile-only, no permission set equivalent
  • Login IP Ranges -- Profile-only, no permission set equivalent
  • Layout Assignments -- Profile-only concept

These will always show as differences because Salesforce doesn't support them on permission sets.

Cannot select more than 5 profiles​

Cause: SimplePerm limits each migration run to 5 profiles to stay within Salesforce governor limits for API calls and DML operations.

Fix: Run multiple migrations. Select up to 5 profiles per run, let it finish, then start the next batch. Each run is tracked separately in the History tab.

CSV export opens with garbled characters​

Cause: The CSV file uses UTF-8 encoding, but your spreadsheet application may be defaulting to a different encoding.

Fix: In Excel, use Data > From Text/CSV (or Data > Get Data > From File > From Text/CSV) and select UTF-8 as the encoding. Alternatively, upload the file to Google Sheets, which handles UTF-8 automatically.

Migration is stuck on "Running" status​

Cause: The migration may be waiting for a Queueable Apex job to execute, or an unexpected error occurred during processing.

Fix: Give it a few minutes -- Salesforce queues async jobs and they may take time to start depending on org load. If the status hasn't changed after several minutes, check Setup > Apex Jobs to see if the SimplePerm Queueable job is queued, running, or failed. Failed jobs show error details there. You can also check the migration's logs in the History tab for error entries.

Need further help?​

For issues not covered here, email support@simplementix.com. Include the migration project ID (visible in the History tab) and any error messages so we can look into it.