Client Mapping lets you choose how clients in a connected integration relate to clients in ScalePad. You can match an integration’s client to an existing ScalePad client, create a new client, or exclude it from syncing.
This helps keep information from different systems together, even when those systems use different names for the same customer. For example, you can map Acme Corporation in your PSA and Acme HQ in your RMM to the same Acme client in ScalePad.
For connections using Client Mapping, you review and commit your mappings before the first data sync.
Supported integrations
Client Mapping currently supports these integrations:
- Autotask PSA
- ConnectWise Manage
- Datto RMM
- HaloPSA
- Microsoft 365 Single-Tenant
- Microsoft 365 Multi-Tenant
This list describes support for the Client Mapping workflow. ScalePad also supports other integrations, which may use a different process for assigning data to clients. The legacy Microsoft 365 Multi-Tenant integration is separate from the Multi-Tenant integration listed above.
Client Mapping appears on eligible connections created while the feature is enabled for your account. An older connection to a supported integration may continue using its existing sync workflow.
How Client Mapping works
After your connection’s credentials are validated, ScalePad discovers the clients available through that integration. Discovery finds clients for you to review; it does not start the full data sync.
ScalePad then suggests mappings based on client names:
- If a name matches one existing ScalePad client, that client is suggested.
- If no existing client matches, ScalePad proposes a new client using the integration’s client name.
- If the name could match more than one existing client, ScalePad leaves the row on Don’t sync for you to review.
Name matching accounts for common formatting differences, but you should review every suggestion before committing it. You can manually select the correct client when the names differ.
In the Map clients section, Their client shows the name from your integration, and ScalePad client shows where that client’s data will be assigned.
- Select an existing ScalePad client: Assigns the integration’s client to that client.
- Create new client: Lets you enter a name for a new ScalePad client, which is created when you commit the mappings.
- Select a client marked (new): Uses a proposed client that has not yet been created. Multiple integration clients can share that proposed client.
- Don’t sync: Excludes that client from syncing through this connection.
You can map more than one integration client to the same ScalePad client when those records represent the same customer.
Set up your mappings
- Open the integration’s setup page. In Integration Center, add a supported integration or open an eligible existing connection.
- Connect and validate your credentials. Use credentials that can access the clients you want to sync. After validation, ScalePad starts finding your clients. If discovery has not started, select Find clients.
- Wait for discovery to finish. The page displays discovery progress and the number of clients found.
- Review the Map clients section. Check each suggested mapping. Use the searchable dropdown to select an existing client, choose Create new client, or select Don’t sync. If your integration has multiple pages of clients, review each page.
- Save any changes. Select Save within the mapping section to store your edits as a draft.
- Commit your mappings. Once your changes are saved, select Commit mappings. This applies your choices and creates any proposed new clients.
- Start a sync. After the mappings are committed, use the integration’s sync control, such as Save and sync now, to import data.
Save and Commit mappings are separate actions. Save stores your draft. Commit mappings makes those decisions active. A new connection using Client Mapping cannot sync until its first set of mappings is committed.
Update mappings or add newly discovered clients
To change an existing mapping, open the connection, update the selection, save your changes, and commit the mappings again.
Your last committed mappings remain active while you edit a draft. Saving a draft does not replace them.
When you add clients in the source system, select Run again to discover them. Review the new rows, save any changes, and commit the updated mappings. Running discovery again preserves your existing mapping decisions.
Take care when changing an already mapped client to Don’t sync. Committing that choice removes the connection’s association with that client, and imported device data from that connection can be removed during sync cleanup.
Troubleshooting
ScalePad couldn’t find any clients
Check that your integration credentials have access to the expected clients or tenants, then select Run again. A discovery run that finds zero clients can still be committed, but nothing will sync through that connection until clients are discovered, mapped, and committed.
Client discovery failed
Check your credentials and the integration’s authentication requirements, then select Try again.
Commit mappings is disabled
Save your pending mapping changes first. The button is also unavailable while a save or commit is processing.
A new client’s name conflicts with another client
Choose the existing client if it represents the same customer, or give the proposed client a distinct name. ScalePad can reject names that are too similar to an existing client or another proposed client.
A selected ScalePad client is no longer available
Choose an available client for the affected row, save, and commit again.
You’re asked to reload before continuing
Reload the page to get the latest mappings, then review your changes again. This can happen when another user has updated the mappings.
You don’t see Map clients
Confirm that you’re using one of the supported integrations above. Older connections may continue using their original workflow, and feature availability can vary by account.
