Error: "This PSA Account has already been mapped for this integration"
Why this mapping error appears, how to find where the PSA account is already mapped, and what to do if you can't find it.
In this article
Why you're seeing this
Account mapping is one-to-one within each integration. Each PSA account can be mapped to only one vendor account per integration. If you try to map a vendor account to a PSA account that's already mapped to a different vendor account in the same integration, Gradient blocks it and shows:
Failed to update. This PSA Account has already been mapped for this integration
The same PSA account can still be mapped once in each of your other integrations. For example, it can be mapped in both Huntress and Pax8.
Step 1: Find the existing mapping
- Go to Data Sources > Advanced Config. You'll land on the Account Mapping tab.
- Filter the Integration column to the integration showing the error.
- Search the list for the PSA account name.
- Check which vendor account it's mapped to. It's often not the name you expect. It might be an old company name, a location, or a person's name, such as a doctor at a clinic.
Step 2: Fix the mapping
- If the existing mapping is wrong: set that vendor account to Unmapped, or map it to the right PSA account. Then map the vendor account you wanted.
- If both vendor accounts belong to the same customer (separate sites, or several Microsoft 365 tenants): Gradient can't map several vendor accounts to one PSA account yet. Each vendor account needs its own PSA account to map to. Add a company or site for each one in your PSA, run a full PSA sync, then map them one-to-one.
Step 3: If you can't find the existing mapping
A mapped account disappears from the Account Mapping list when either side becomes inactive, but the mapping stays in place. This is the most common reason partners see this error for an account that "isn't mapped anywhere."
- Check that the PSA account is active in your PSA. Inactive and Prospect accounts won't show.
- Run a full PSA sync from Settings > Data Settings > PSA Configuration > Start Full Sync, and wait for it to finish.
- Try mapping again.
Still stuck?
Contact support if any of these apply:
- The account is active in your PSA but still doesn't show.
- The account was renamed and you can't find the old mapping.
Email support@meetgradient.com with:
- The integration name
- The vendor account you're trying to map
- The PSA account name
- A screenshot of the error
We can find the old mapping and clear it for you.
Related articles