If you see more clients in Lifecycle Manager than expected, use the steps below to identify where the clients are coming from and reduce duplicate or unwanted clients.

How are clients created?

Lifecycle Manager creates a client when it syncs at least one supported data type from a connected integration, such as hardware assets, software assets, contacts, Security Awareness Training (SAT) data, Endpoint Detection and Response (EDR) data, or Customer Satisfaction (CSAT) data. 

For more details, see Understanding Lifecycle Manager data syncing.

Where are the extra client(s) coming from?

Before checking specific causes and solutions below, you first need to know which integration(s) are syncing the clients into Lifecycle Manager:

1. Navigate to your Client Settings page

2. Click the 3 dots to review the integration source(s)

3. Use the source information to choose the appropriate resolution below

Common causes and solutions

1. Duplicate clients

Lifecycle Manager matches clients across integrations only when their names match exactly. For example, Acme Inc. in a PSA, Acme in an RMM, and Acme Inc in SAT integrations are treated as three different clients.

This can create duplicate clients, with each client containing data from a different integration. This prevents consolidated data from appearing in reports and deliverables.

Reviewing client names and consolidating duplicate records is a vital part of Lifecycle Manager data management - especially for new users or when setting up LM for your new clients.

Identifying and Merging Duplicate Clients

Option 1: Rename your clients to match across systems (only if feasible)

• If feasible, you can avoid merging in-app by renaming the clients in your integrations to match exactly
• We always suggest this if only a handful of clients are affected and you want name alignment across systems anyway, but we recognize it's not always possible / too much work to do this.

Option 2: Use AI to ID duplicates (fastest)

1. Download the Client Summary Report from the Clients page
2. Ask your preferred LLM (ChatGPT, Claude, etc.) to create a spreadsheet for you of likely dupes
3. Work through the list on your Client Settings page, merging from the parent record (screenshot e.g. below) - this is the fastest way to merge in our app today

Tip: If any of the clients to merge have an LMX license assigned, use them as the parent.

Option 3: Manually work through client list (slower)

1. Navigate to your Client Settings page
2. Identify a duplicate client - usually obvious as it's alphabetically ordered
3. Merge clients into the parent by clicking the 3 dots and merging

• For more information on merging, see: Merging and renaming Clients

2. Inactive or old clients with active hardware

An old client can remain in Lifecycle Manager when an integration continues to sync an active hardware asset or another supported data type for that client.

After you identify the source integration:

1. Identify where the client is coming from (see section above)

2. Open the client in the source integration identified in step 1.

3. Review the client’s status and the status of its associated assets.

4. Deactivate the client and any old or unwanted assets in the source integration.

5. Run a manual sync in Lifecycle Manager, if you want the change to appear sooner.

After you mark a client or its assets inactive in the source integration, Lifecycle Manager removes them upon the next sync.

For more information about sync timing and manual syncs, see Understanding Lifecycle Manager data syncing.

3. Active clients you don’t want to manage in Lifecycle Manager 

Some clients are technically active in an integration but aren’t clients you want to manage in Lifecycle Manager. For example, they might be test organizations or clients with less active MSP service relationships.

To exclude these clients, review the client-level sync settings for the integration that is providing them:

1. Identify where the client is coming from (see section above)

2. Open the integration identified in step 1 on your Integrations page

3. Review the settings that control which clients or organizations sync, such as company or organization type and status.

4. Uncheck the values that include clients you don’t want to sync.

5. Click Save and sync now to start a fresh sync.

Note: the available filters vary by integration. Some integrations (e.g. RMMs) do not allow filtering at the client level. You cannot remove clients from the RMM sync without removing all RMM hardware agents for those clients.

If you don't have what you need to remove these clients, but still want to, we may have a workaround for you. Please submit a support ticket and we will help!

4. Pricing concerns caused by too many clients

If you’re reviewing this article because you’re concerned about pricing, on 08/24/2026 newer partner accounts can select which licenses apply to which clients. The system won’t automatically move these accounts to a higher license tier based only on an increase in their client count.

If you don’t see this functionality in your account, contact your Account Manager. They can help update your account to the newer licensing system.

Still seeing too many clients?

If you still see unexpected clients after reviewing this article, contact the Lifecycle Manager Support team by submitting a support ticket. Include the following information:

• The name of an unexpected client in Lifecycle Manager.

• The integration source shown for that client.

• A full-page screenshot of the same client in the source integration.

• Any recent changes to the client’s name, status, assets, or sync settings.

Any questions?

Reach out to the Lifecycle Manager support team by submitting a support ticket.