Deprecation of Old Client Mapping – MSPbots.ai

Background information

The new version of Client Mapping, capable of reading names across integrations and automatically generating mappings, was released on January 16, 2025. Data from the old version has been successfully migrated to the new version.

The old version is now deprecated and has been switched to read-only mode. A transition period is available for users to migrate their assets. Dashboards and Slicers associated with the old version will continue to operate until further notice.

Impact on different clients

Clients not using the old version can access the new version to get started.
Clients using the old version:
- The old assets will continue to operate, so there is no need to worry.
- The migration from the old version to the new version has been done.
- If you want to check the migration report and handle any failures, refer to How to access the migration report.

What is the impact on the old version

Old version will still be working, separately with new version.
The names mapped in the old version will be retained, and assets using them will still function normally.
The old version will be in read-only status.
If you want to update the mapped names, you can do so in the new version.
Please note that names that fail to migrate will only be available in the old version.

How to utilize mapped names from old version in the new version

Successfully migrated names from the old version will be available in the new version and in assets built for the new version.
Names that failed to migrate can be reviewed and handled manually in the migration report, refer to Failed migrations.
Updates you make to names in the new version will automatically sync to the old version and be reflected in the old assets.

How to access the migration report

Go to Settings > Automated Client Mapping.
Click Migration Report.
The page displays the migration information of old client mapping to the new version, including details on successful migrations and failed migrations.
- For successful migrations, you can view them in the list.
  - These exist in both the new and old versions.
- For failed migrations, you can see the failed reasons in the list.
  - These only exist in the old version.
  - If you no longer need them, you can delete them.
  - Reasons for migration failure include:
    - The name does not exist in the primary data source.
    - Name mapping conflicts.
    - Issues related to SQL Agent, Dropbox or OneDrive integration.
  - If you have fixed the errors, you can try migrating again. Delete the failed items first and then click the here link to remigrate.