Lifecycle Manager reports an inconsistent client name when the same hardware asset is associated with different clients across connected integrations. This can happen when client names differ, an asset is assigned to the wrong client at a source, or duplicate source records disagree.

Review the affected hardware

1. Open the Issues page.
2. Open the inconsistent client names issue.
3. Expand Affected hardware in the issue to review the devices and the client and integration values that conflict.
4. Use the integration link for a device when you need to inspect or correct its source record.

The affected-hardware list is the quickest way to identify the exact records involved; you do not need to compare every client or device manually.

Resolve the client assignments

Choose the resolution that matches the data:

• Merge matching client records in Lifecycle Manager: Use client merging when two imported client records represent the same client. Merging consolidates them in Lifecycle Manager without renaming the organizations in their source systems.
• Correct the source assignment: If a device belongs to the wrong client, update or remove the record in the connected integration.
• Standardize source names: If required by your workflow, update the client names in the source integrations and allow them to sync again.

Check for duplicate assets

Duplicate source records can also associate one device with conflicting clients. Follow How to eliminate duplicate assets to find and correct duplicates in the source integration.

Sync the corrected data

After correcting source data, run Sync now from Lifecycle Manager. Reopen the issue after the sync completes to confirm that the affected hardware no longer appears.

NEW Join our MSP Power-Ups - Free 15-minute micro-workshops + live Q&A with our Lifecycle Manager experts. Sign up here to reserve your spot.