Exporting reports from Sugar is a helpful way to review, analyze, and share focused data outside the application. But once the report data is opened in Excel or another spreadsheet tool, the results may not always look the same as they did in Sugar.
This does not always mean something is wrong with the report or the export. In many cases, the difference stems from how Sugar organizes report data versus how spreadsheet tools interpret exported CSV files.
Report exports are especially helpful when users need a focused dataset rather than a broad module export.
From a module list view, you can export selected records, the current page, or all records returned by the active search or filter. However, list view exports do not include related records. Report exports offer more control by letting you choose fields, apply filters, and pull in data from related modules. As a result, they are better suited for answering specific business questions, preparing data for analysis, or sharing a targeted dataset.
Report exports can also be useful when users need to work with Sugar data in another tool, such as Microsoft Excel. In some cases, exported report results may also be used as part of a cleanup-and-reimport process, especially when Record IDs are included.
What to check when you're exporting a report?
Before exporting, make sure the report type matches the question the user is trying to answer.
|
Report type |
Best used when users need to… |
|
Rows and Columns |
Review detailed records in a table-style layout. |
|
Summation |
See grouped totals or counts. |
|
Summation with Details |
See summarized groups with supporting detail records. |
|
Matrix |
Compare grouped values across rows and columns. |
This matters because users may expect the export to behave like the report display. However, a report built for grouped insight is not the same thing as a simple flat list of records.
If a user cannot export a report, start by checking access. The Export option may not appear if Export permissions are restricted. An administrator may have limited export access via roles or configured permissions, allowing only certain users, such as the report owner, to export. In other cases, export may be disabled, preventing the option from appearing in the Report action menu.
Before assuming there is an issue with the report export, confirm:
A common export concern is that the totals in Excel do not match what users saw in Sugar.
This usually happens because Sugar and Excel may be showing the data at different levels.
Sugar reports may display grouped or summarized data. After export, Excel displays the underlying rows in the CSV file. If the report includes related modules, the same primary record may appear more than once because it is connected to multiple related records. Excel then calculates based on the rows it sees, which may produce a different result than the grouped total shown in Sugar.
The export is not necessarily incorrect. The data may be presented differently.
If two users export the same report and get different files, check the report design before assuming there is a problem.
Differences may come from:
This is especially important when reports are shared across teams. The report may be working correctly, but each user’s access or filter values may produce a different export.
Shared reports can be useful, but they can also create confusion when users export results without understanding the report logic. For shared reports, consider whether the report includes dynamic filters such as Current User. This filter allows one shared report to show each user only the records assigned to them.
This can be helpful because one report can serve many users. However, it also means two users may export the same report and receive different results.
That is expected behavior when the report is designed to respond to the logged-in user.
|
Topic |
What to remember |
|
Export permissions |
Users must have export privileges. If Export is missing, check roles and system settings. |
|
Report exports |
Reports provide a more focused export than module list views. |
|
Row-level validation |
Use Rows and Columns reports when users need to compare exported rows against Sugar. |
|
CSV format |
CSV files are plain text files that spreadsheet tools convert into rows and columns. |
|
Grouped totals |
Sugar may show grouped or summarized data, while Excel displays raw rows. |
|
Related modules |
Related records may cause repeated rows in the export. |
|
Excel calculations |
Excel sums the rows it sees, which may differ from Sugar’s grouped totals. |
|
Formatting issues |
Rounding, decimals, dates, delimiters, and multi-line text fields can affect how data appears. |
|
Record IDs |
Include Record IDs if exported data may be updated and re-imported. |
|
Large exports |
Break large reports into smaller batches if the export times out. |
Exporting a report does not change the data in Sugar. It changes how the data is viewed outside Sugar.
Want a quick walkthrough of how report exports work and why your Excel totals may look different from what you see in Sugar? Watch the video below, then download the Admin Export Checklist and use it the next time you need to validate exported report data.
548 Market St PMB 59423
San Francisco, California 94104-5401