Autotask Data Migration Guides

How to Create an API User in Autotask PSA?

To run an Autotask data migration, you need to create an API user in Autotask PSA with a corresponding security level. Below are the steps to create a security level for an API user in Autotask PSA:

How to Create a Security Level for API User in Autotask PSA

1. Go to Admin and select Account Settings & Users / Client Settings & Users within the Admin Categories section.

2. Expand the Resources/Users (HR) settings and select Security Levels in the Security section.

3. Locate the bullet list icon next to the API User (system) (API-only) record and select the Copy action.

4. Name the security level and click Full Permission in the Web Service API section.

5. Tap Save & Close at the upper left corner.

How to Create an API User in Autotask PSA

1. Hover over Admin and select Resources (Users) in the Commonly Used section.

2. Hover over New and select the New API User option.

3. Fill in the General fields. Expand the Security Level options and select the one you’ve recently created. You can generate the Username and Secret or write them manually.

4. Scroll down to the API Tracking Identifier and pick Relokia - Data Migration as Integration Vendor.

5. Click Save & Close.

Once you’ve created an Autotask API user with the necessary security level, you can proceed to automated data migration.

How to configure a user security level in Autotask

During an Autotask migration, there might sometimes occur a problem with comments import – the comments you try to transfer cannot be created on this platform. This happens because of the security level discrepancy.

To eliminate the error, change the security level of the agent who wrote the comment so they have permission to perform actions on tickets assigned to the agent running the migration.

Do this in a few easy steps:

• Choose the Admin category on the left-side Autotask dashboard.
• Open Account Settings & Users section.
• Click on Resources/Users (HR) → Pick Resources/Users from the tab.
• Find the agent whose comment is not displayed during transfer and check their security level (it’s indicated in one of the columns on the right).

Then:

• Go back to the Account Settings & Users section and choose Security Levels.
• Find the security level associated with your agent.
• Click on the 3 horizontal lines icon to the left of the level → Pick Edit.
• Scroll down to Web Services API and click on it.
• Select Resource Impersonation from the drop-down menu and select the checkbox for “Allow impersonation of resources with this security level” → Save the changes.

The steps above should fix the issue – unless it’s a system level. Those tend to throw an error “This security level is not editable”. Thus, there is no “Allow impersonation” box to check.

But there is, of course, a way to untie this knot as well:

• Click on the three-line menu next to the required security level again and choose Copy.
• Go down to Web Services API and check the box next to “Allow impersonation of resources with this security level” → Save the changes.

Done! The box is checked. But these changes will not be recognized by Autotask because you edited a copy, not an original security level. That is why you also need to take the following steps:

• Go back to Resources/Users → Pick an agent with the same security level you just copied.
• Click on the agent’s name so that their profile window opens;
• Navigate to their Security section → Open the Security Level drop-down menu;
• Choose a security level you need to grant access to the comments section (should be the same one as the agent running the migration);
• Save the changes.