Licenses are the largest controllable line in most CRM budgets, and also the least looked after. Seats get assigned during rollout, people change jobs, projects end, and nobody goes back to check who still needs what. By the first renewal the organization is often paying for accounts that are unused, mismatched to the person’s actual needs, or tied to people who have left.

This guide gives IT and business leaders a repeatable process for keeping licenses aligned with reality, without making assumptions about any vendor’s pricing.

Establish a Source of Truth

You cannot manage what you cannot list. Start with a complete user export from the CRM, including each user’s license or edition type, status, last login, role and manager. Then compare it with your HR roster or identity provider. Three categories typically emerge:

• Active users with a clear business need
• Users who exist in the CRM but not in the HR or identity system, such as departed staff or untracked contractors
• Valid employees who rarely or never log in

The second group is both a cost and a security concern. The third group needs a conversation, not an automatic removal.

Understand License Types Before Cutting

Vendors commonly offer several license tiers: full-featured, limited, read-only, or platform-specific. Check the vendor’s current documentation and your contract for what each type permits and whether users can be moved between them. Often the cheapest saving is not removing a user but changing a person who only views dashboards from a full license to a lighter one, if the contract allows.

Be careful about compliance. Downgrading a user who still performs actions the lighter license does not allow can create contractual issues, so confirm entitlements before changes.

Define “Inactive” Sensibly

Login recency alone misleads. A finance reviewer who looks at reports quarterly is active in a meaningful sense, while a salesperson who logs in daily but never records anything may not be. Combine signals: last login, record creation and editing activity, report or dashboard use, and whether the user is a named approver in a workflow.

Set your inactivity thresholds with business owners, and treat the first review as a conversation starter rather than a purge.

A License Review Table

Finding	Likely Meaning	Suggested Action
Account with no matching employee	Leaver or untracked contractor	Disable promptly, then reclaim the license
Employee with no recent activity	Role change, low need, or poor adoption	Ask the manager; downgrade or reassign
Full license, mostly viewing	Over-licensed	Move to a lighter type if permitted
Shared login	Compliance and security risk	Replace with individual accounts
Service or integration account	Needed but unowned	Assign an owner and document purpose
Pending seats never assigned	Unused purchase	Hold or release at renewal

Make Joiners, Movers and Leavers Systematic

Most license waste comes from process gaps. Tie CRM provisioning to your identity system so that new hires get the correct license type from a role template, and departures trigger removal automatically. For internal movers, define what happens to the license, permissions and record ownership when someone changes teams. Reassigning record ownership before deactivating a user also prevents orphaned records and broken automations.

Plan Around Renewal Dates

License counts are most flexible before renewal. Note the notice period required to reduce seats, and calendar your review well ahead of it. Many contracts require advance notice, and missing the window can lock you into the previous quantity. Check how the contract treats adding seats mid-term versus removing them, and whether there are minimums.

A Realistic Example

Consider a hypothetical company with a hundred CRM seats, a number it chose at launch. The review compares the user export with HR data and finds several accounts belonging to people who left, a group of managers who only ever open dashboards, and a few seats used by people who had changed departments and no longer sell.

The administrator disables departed accounts, proposes lighter licenses for dashboard viewers subject to contract terms, and asks managers to confirm the rest. At renewal, the company negotiates a seat count based on verified need rather than the original rollout estimate, and sets up a quarterly check so the cleanup does not need to be repeated from scratch.

Do Not Forget Add-Ons and Sandboxes

Licenses are not just user seats. Review add-on modules, extra sandbox environments, premium support tiers, and storage allocations. Each may be priced separately and each is easy to forget. Ask whether every paid add-on has a named business owner and a use that you can describe. If nobody can, it is a candidate for removal at renewal.

Report Simply to Leadership

Keep reporting short: total seats, active seats, seats by license type, accounts flagged for action, and the planned changes before renewal. Leaders do not need a dashboard of dozens of metrics; they need to know whether the organization is paying for what it uses and what is being done about the gap.

Frequently Asked Questions

How often should licenses be reviewed? Quarterly is a sensible rhythm for many organizations, with a deeper pre-renewal review well ahead of the notice deadline.

Is it safe to remove users who have not logged in recently? Not automatically. Confirm with the manager, since some roles legitimately use the system infrequently, and check workflow approvals and integrations before deactivating.

Can we reassign a seat from a departed user to a new hire? Often yes, but the rules depend on your contract and vendor, so check the current terms.

Who should own license management? Typically the CRM administrator or an IT asset or SaaS manager, with finance informed and business owners confirming need.

What if teams resist losing their licenses? Frame it as matching access to need, and make restoring a license quick and easy when a real need appears.

Next Step

Export your CRM user list today and match it against your HR roster. Even this single comparison usually reveals accounts that can be closed, and it gives you a baseline for the rest of the process.