Record Limit
A record limit is the maximum number of records a CRM, data tool or account can store, sync or process. Some tools count only one object, such as contacts, which is why the term is often called a contact limit. Others add up records across several objects, such as contacts, companies and deals, and some count records from more than one connected system.
The count behind a record limit includes every record that meets the tool's rules, whether it describes a new customer or repeats one already stored. A person entered twice takes two places in the count. That makes the record limit as much a data quality measure as a capacity setting: an account full of duplicates reaches its limit sooner, and its record count says less about how many real customers it holds.
See how Dedupely counts the records you sync in your CRM
What Is a Record Limit?
A record limit is the ceiling on how many records an account can hold or work with at one time. It applies to the records a tool stores or connects to, and the count goes up as records are created, imported or synced, and down as they're merged or deleted.
What counts as a record depends on the tool. A record can be a contact, a company, a deal or a ticket in HubSpot; an account, a contact or a lead in Salesforce; a person, an organization or a deal in Pipedrive; or a lead or an opportunity in Close. Some tools count only one of these, such as contacts or leads. Others add up every object they hold or sync, so a team with contacts in one CRM and accounts in another may have both in the same count.
A short example shows how duplicates affect the count. Acme has 10,000 contact records. J. Smith was created once from a web form and again from a trade show import, and about 800 other people are in the CRM twice in the same way. The record count says 10,000, but the account holds about 9,200 real people. Those 800 extra records use up part of the record limit without adding a customer.
A record limit also sets which work fits in an account. Turning on another object, connecting another system or running a large import adds records to the count, so teams often check what's counted before adding data.
How a Record Limit Works
A record limit works by comparing the number of counted records with the maximum the account allows. A few steps decide that number:
- The tool decides what counts. Some tools count records in one object, such as contacts. Others count every object that's stored or turned on, and add records from several connected systems together. Some tools also leave certain sources out, such as uploaded files.
- Records enter the count. Records join the count when they're created, imported or synced. In tools that sync from a CRM, some sync a whole object at once, so turning that object on adds all of its records, while others sync a filtered part of an object.
- The count changes over time. New form fills, imports and integrations add records. Merging removes the extra records in a duplicate set from the CRM, and deleting or archiving removes others, so a count based on the CRM's records goes down after a cleanup.
- The tool responds at the limit. What happens when the count reaches the limit varies. Some tools stop accepting new records. Others pause certain actions while the rest of the tool keeps working, so data can still be searched and reviewed.
Because duplicates enter the count the same way as any other record, the record count reflects how clean the data is, not only how many customers there are.
Why a Record Limit Matters for CRM Teams
A record limit decides how much data a team can work with in one account, so the records in the count shape what's possible. When duplicates make up part of the count, the account reaches its record limit sooner than its real customer base would. Room that could hold new leads, another object or a second CRM is taken by records that repeat ones already stored.
The record count is also a number people report on. A contact count that includes duplicates overstates the size of the database, and any figure built on it, such as contacts per account or the size of a segment, is off by the same amount. Two records for one person can also be counted in two lists, sent the same email twice or assigned to two owners.
Reaching a contact limit can also stop day-to-day work. Depending on the tool, new records may not come in, an import may not finish, or some actions may wait until the count changes. A team close to its limit then has to decide which records to keep or which objects to leave out, often without knowing how many of the records are duplicates.
Keeping duplicates out of the count turns the record limit into a clearer number: it tracks real people, companies and deals, and it leaves room for the data the team actually needs.
Getting Started With Record Limits
Start by finding out what your tool counts. Check whether the record limit covers one object or several, whether records from more than one connected system are added together, and whether any sources, such as uploaded files, are left out. That tells you which records actually affect the count.
Then choose which data needs to be in the count. Some objects matter for the work at hand, and others can stay out until they're needed. When an object syncs as a whole, turning it on adds all of its records, so check its size first.
Next, look at how much of the count is duplicates. Running a duplicate search on your largest objects shows how many records repeat others, and merging those sets brings the count closer to the real number of customers. Keep new duplicates from entering the count by checking the forms, imports and integrations that create them, and run the search again after large imports.
In Dedupely, the record limit counts the records you sync, adding up every active object across all connected CRMs, and you can turn objects on or off to choose what's in the count. Records from CSV files don't count toward it, so a spreadsheet can be checked for duplicates without using any of the limit.
Key Takeaways: Record Limit
A record limit is the maximum number of records a tool or account can store, sync or process. Tools differ on what counts: one object such as contacts, several objects, or records from more than one connected system. Duplicates count like any other record, so they use up part of the limit and make the record count look larger than the real customer base. Checking what's counted and merging duplicates keeps the count accurate. In Dedupely, the record limit counts the records you sync, adding up every active object across all connected CRMs, and objects can be turned on or off. CSV records don't count. If the limit is reached, merging pauses, while searches, matching, scans, Merge Rules, previews and Auto Match keep working.
Frequently Asked Questions About Record Limits
Do duplicate records count toward a CRM's contact limit?
Yes. In a tool that counts contacts, a duplicate is a contact like any other, so it takes a place in the count even though it describes someone already stored. That holds whether the CRM is HubSpot, Salesforce, Pipedrive or another tool with a contact limit: the count doesn't know that two records describe the same person. An account with many duplicates reaches its contact limit sooner, and its contact count says more people are in the CRM than there really are. Merging duplicate sets removes the extra records from the CRM, so the count goes down once the cleanup is done. The same applies to other objects, such as companies or deals, when they count toward a limit. In Dedupely, duplicates are synced records like any others, so they count toward the record limit too. Duplicate Searches find them in each synced object, and Merge Rules decide what each merge keeps before the extra records are removed.
What counts toward a record limit when several CRMs are connected?
It depends on the tool, so check whether it adds records across systems or counts each one on its own. Some tools set a separate limit for each connected CRM or each object. Others add every connected system's records into one total, so connecting a second CRM or turning on another object raises the count. In that case, the objects you choose to connect matter as much as the size of each one. A large object you don't need for the work at hand can take up a big share of the limit. In Dedupely, the record limit adds up the records in every active object across all connected CRMs. For example, 15,000 HubSpot Contacts, 18,000 HubSpot Companies and 20,000 Salesforce Accounts count as 53,000 records. Objects can be turned on or off, and a whole object syncs at once, since part of an object can't be synced on its own.
Do spreadsheet records count toward a record limit?
That depends on the tool. Some data tools count uploaded files the same way as records synced from a CRM, while others count only the CRM records and leave files out. If a tool counts uploads, checking a large spreadsheet for duplicates can take up as much of the limit as a CRM object of the same size. That matters for teams that clean a list before importing it into the CRM, since that's often when a file is largest and has the most duplicates. Cleaning the file before import also keeps its duplicates from entering the CRM's count later. In Dedupely, records from CSV files don't count toward the record limit, and CSV uploads are unlimited. A spreadsheet works the same way as a CRM for finding duplicates: you can match its rows, merge them and export the clean data, then import a clean list into the CRM.
What happens when an account reaches its record limit?
It depends on the tool. Some tools stop accepting new records, some block imports or syncs, and others pause certain actions while the rest of the tool keeps working. The data already in the account doesn't disappear, but the work that adds or changes records may wait until the count changes. Checking the record count before a large import or before connecting another object helps avoid reaching the limit in the middle of a project. Because duplicates are part of the count, merging them is one way to bring the count down. In Dedupely, reaching the record limit pauses merging. Duplicate Searches, matching, scans, Merge Rules, previews and Auto Match keep working, so you can still find duplicates, review the sets and set what each merge keeps while merging is paused. Connecting or syncing never merges, edits or deletes anything in the CRM.
How do you keep a CRM's record count accurate?
Merge duplicates on a regular schedule and fix the sources that create them. A record count stays accurate when each person, company or deal appears once. Start with the largest objects and the clearest duplicate sets, such as records that share an email address, and merge those first. Then look at where new duplicates come from, such as repeat form fills, imports or an integration that creates a new record instead of updating one. Run duplicate checks again after large imports, and remove records that no longer belong in the CRM. In Dedupely, Duplicate Searches find the duplicate sets in each object, and Merge Rules decide what each merge keeps. Auto Match and Auto Merge keep new duplicates in check: Auto Match notifies you when new matches reach a count you set, and Auto Merge merges new duplicates on a schedule you choose. Merges can't be undone, so set your Merge Rules first.
