Before moving CRM call review files, check field-list limits, rich text truncation, and the destination's import limits, then test a small sample.
Key takeaways
- Count the fields your move needs.
- Compare long summaries with the CRM originals.
- Test a small import before moving the full file.
If you manage a B2B software sales team, you have probably lived this. A rep's call review notes sit in the CRM. You need them in a spreadsheet for a coaching session, or in a file for a quarterly review, so you export them, paste them, or pull them through a script. A few weeks later someone notices a summary that stops mid-sentence, or a column that is blank for half the calls. Nobody meant to lose anything. The CRM and the file format each have limits, and those limits are rarely visible on the screen where you click Export.
This post covers three caps to check before a rep's call review file moves. You do not need to be an engineer to check them. You need to ask a few questions before anything moves, and run a small test first. The examples draw on two vendors' official documentation, Zoho CRM and HubSpot, but the habits work with whatever tools your team uses.
What the file is for
Before you touch a tool, decide what the file must do. A coaching file and a compliance file need different things. Ask who will open it, what decision it supports, and how stale it can be before it stops being useful. Write those answers down in one sentence. That sentence becomes your test: if the file cannot support the decision, the move has failed, even if every row arrived.
Next, list the fields the decision depends on. Separate the fields you need every week from the ones you check once a quarter. The first group must arrive intact on every move. The second group can wait for a fuller export. This split matters for the caps below, because the more fields and text you try to move at once, the more chances there are for one of the limits to bite.
Cap 1: the field list has a ceiling
A call review is rarely one field. A typical review form might include the call date, the rep's name, the account, the deal stage, the next step, a few scores, and a free-text summary. When a tool pulls records out of a CRM, it often asks you to name the fields you want. The list you give it is only as complete as your review form.
Zoho CRM's developer documentation for its Get Records API says that you can include a maximum of 50 field API names in that parameter ( Zoho CRM, "Get Records"). That limit applies to a single request. It does not tell you how many fields a record can hold. A review with more fields than that needs more than one pull.
Here is what to check:
- Count the fields in the review form, including the ones reps fill in rarely. Those are often the ones managers end up needing.
- Compare that count with the field limit of the tool you use. If your export tool or script calls a vendor API, read that API's documentation for its field-list limit.
- When a tool asks for field names, use the exact API names from your CRM settings, not the labels reps see on screen.
- Keep a short written list of the fields each pull covers. When someone asks why a column is empty, you can answer from the list instead of guessing.
Splitting one large pull into two or more smaller pulls is a common fix. Then join the results on a stable record ID, so each call review lands on one row. Check that the row count matches the number of calls you expected, and if it does not, find out why before the file goes to anyone else.
Cap 2: long summaries get cut short
The most valuable part of a call review is usually the free-text summary: what the buyer said about budget, which objection came up, and what the rep promised to send next. Reps write these as paragraphs, sometimes with bullets, bold text, and links. A long summary may sit in a rich text field, which holds formatting as well as words, so check which field type your CRM uses for summaries.
Zoho's Get Records documentation states that in the response of the Get Records API, rich text fields are truncated to display only the first 500 characters ( Zoho CRM, "Get Records"). Whatever sits at the end of a long summary, often the next step, may not make it into the file.
This is the kind of failure that looks like success. The spreadsheet has a value in every row, so nobody notices until a coaching conversation depends on a missing sentence. A cell that is full looks complete. Check it on purpose.
Four checks help:
- Pick three of the longest call reviews from the last month. Compare the full text in the CRM record with what lands in your file, looking closely at the last lines.
- Look for summaries that stop mid-sentence, bullet lists that end early, and next steps that are missing.
- If a script moves the text, flag any value that is exactly 500 characters long. Open those records in the CRM and compare them with the file.
- Check that line breaks survive the move. Formatting such as bold text and links often does not carry into a plain spreadsheet cell, so decide in advance what you will keep.
A habit for reps helps too. Ask them to put the decision-relevant facts in the first sentences of each summary. If a cut happens, the shortened version still says something useful, and the most important facts are not the ones that disappear.
Cap 3: import files have row, queue, and encoding limits
The third cap applies when the file goes into HubSpot. HubSpot's guidance on formatting import files ( HubSpot, "Format import files") lists several limits. Five of them matter most for a call review file:
- If you start 4 or more simultaneous imports, they will be queued.
- Up to 2 of these imports can be greater than 10,000 rows.
- Files with more than 500,000 rows take multiple days to complete.
- You can import up to 10,000,000 rows daily, with a limit of 1,048,576 rows in each file.
- Use UTF-8 encoding if the file includes foreign language characters.
Queues. If several people on your team start imports at the same time, expect some to wait. Agree on who imports what and when, especially when many people want their reviews in the same place.
Size. A single team's reviews may sit well below these limits. A full-history export is different. A year of reviews across several teams can grow quickly. Plan a backfill on a timeline, not as a same-day job.
Daily and file totals. Split a file well before its row limit, so that one error does not force a rerun of everything. Keep a running count of rows across the day so you do not discover the daily total at the end.
Encoding. Call reviews often include names of people and companies, and some of those names use foreign language characters. A file saved in a different encoding can come through with garbled text, and nobody may notice until a rep says a name looks wrong.
Before any import runs, check these in order:
- Confirm the row count, and split the file if it is large.
- Confirm the file is saved as UTF-8.
- Check the import queue. Who else is importing, and is anything already running?
- Import a small sample first and check it against the source.
- Record the import: date, file name, row count, and who ran it.
Illustrative example: checking a review file
Consider a manager who needs call reviews before a quarterly review. The review form has more fields than the manager expected, and some summaries run long. The manager does not want to guess which values are complete, so they walk through the checks in order.
First, the field count. The manager lists every field on the form and compares that list with the names the export script requests. Suppose the list is longer than a request can name. The manager splits the pull into smaller requests and labels each output file with the fields it covers.
Second, the long summaries. The manager compares each with the CRM record. Some values are exactly 500 characters long. The manager flags them for comparison before using the file.
Run a test move before the real one
A test move is the cheapest way to find a cap before it finds you. Pick one rep's call reviews from a single week. That is enough to show whether the fields, the summaries, and the row count all survive. Keep the test small, but make it realistic: include a long summary, a review with empty fields, and one with characters that are not plain English letters.
Write down the expected values before you run it. For each test record, note the number of fields you asked for, the length of the summary in the CRM, and the number of rows you expect in the file. Then compare what you got with what you wrote down. A mismatch is useful information. It tells you which cap you hit, and you can fix that one before the real move.
Then do the real move in a window when nobody else is importing. Keep the source record intact. Do not delete the CRM original until the file has been checked and the people who use it have confirmed the numbers. This sounds obvious, but it is the step people skip when a deadline is close.
Common mistakes to avoid
Most problems come from a few habits, not from the tool. Watch for these.
- Trusting the first pull. A pull that returns rows looks finished. Check the field count, row count, and the last line of a few summaries before you call it done.
- Editing the spreadsheet and assuming the CRM changed. A change in the file does not update the record. Decide which copy is the one you edit, and say so in your team's notes.
- Importing without a plan. Several managers importing on the same afternoon can lead to queues and confusion about which version is current. Name one owner for each import.
- Trusting a sample you did not choose. A random sample of short reviews may miss long summaries. Pick samples on purpose, including the longest and the most complicated records.
- Letting one person hold the only copy. If the only version of a quarter's reviews sits on one laptop, a single error is hard to trace back. Keep the CRM as the source, and store the file where your team can find it.
Keep the CRM as the record
Your CRM should stay the system of record, and the spreadsheet should be a copy made for a purpose. When the two disagree, check the CRM first. That keeps the coaching conversation tied to what actually happened on the call and what the rep actually logged.
Rules and limits change, so treat every number in this post as a snapshot. Before you rely on a limit, open the current vendor page and check it yourself. Your CRM admin can also tell you how your team's exports are set up.
Today, pick a small test file, write down its expected fields and rows, and compare the result with the CRM before moving the full file.
Related guides: Call review folders: 4 limits to check before sharing · Shared proposal file caps: 4 limits to check before sending · CRM data ownership: 4 checks before coaching notes.
Common questions
Does an export with every row mean the file is usable?
No, the file must also contain the fields and full summaries needed for the decision it supports.
What should you do when a summary stops mid-sentence?
Compare it with the CRM original before using it in a coaching conversation.