Export a weekly pipeline snapshot in 4 systems

• Save each file before its access window ends. HubSpot export links expire after 30 days, according to HubSpot. Pipedrive exported files are available for 28 days, according to Pipedrive. Close links expire automatically after 7 days, according to Close.
• Row limits are system-specific. Microsoft allows up to 100,000 rows at a time for static worksheet exports, according to Microsoft. Do not apply this limit to other platforms.
• Activities and notes are not included in standard deal exports. In Pipedrive, activities, notes, and files linked to deals and contacts must be exported separately, according to Pipedrive.
• Save the file immediately after export. Because links expire, download the file to your local drive before the deadline. Record the export date and filter settings used to generate the snapshot.
• Verify scope before downloading. Confirm the view and filters match your intended pipeline scope. A static export captures only the current state of the records at that moment.

Saving a reliable weekly snapshot requires defining the exact data scope before initiating the export. In Close, the process begins by selecting the specific record type you need, such as Leads, Contacts, or Opportunities. You must also decide on the file format, which can be either CSV or JSON, and determine whether the export should include only common fields or all available fields according to Close. These choices define the structure and content of the file you will receive.

Once the export is generated, the system provides a download link for the file. For privacy reasons, this link will expire automatically after 7 days according to Close. This expiration creates a specific deadline for saving the file locally. If the link expires before you download the file, you will need to generate a new export to access the data. The snapshot reflects the state of the records at the moment the export was created, not the current state of the CRM after the download.

To manage this process effectively, write down the specific records, filters, and columns needed for the current week before starting the export. Save the resulting file locally with the export date included in the filename. This practice ensures you have a clear record of what data was captured and when. The download link expiration is a separate concept from export log retention or API rate limits. Focus on the immediate action of downloading the file within the 7-day window to secure the snapshot for your weekly review.

The tables below list the specific export constraints for the four systems covered in this guide. Rows show only the limits those publishers document for that column.

Microsoft allows exporting up to 100,000 rows at a time, according to Microsoft. This limit applies specifically to the static worksheet export feature described in the documentation. Do not assume this row cap applies to other CRM platforms or export methods.

HubSpot imposes column limits based on file format: 256 columns for XLS files and 16,384 columns for XLSX files, according to HubSpot. Additionally, HubSpot expects multiple files when exporting CSV or XLSX files with more than 1,000,000 rows and XLS files with more than 65,535 rows, according to HubSpot. Download links to HubSpot export files expire after 30 days, according to HubSpot.

Before clicking export, open the specific list view that matches your weekly snapshot needs and apply the filters that isolate the exact records you require. In Pipedrive, the process begins by opening a relevant list view and applying a filter to show the data you want to export, as stated in the Pipedrive documentation. This step ensures the export scope is defined by your active view rather than the entire database.

However, having export permissions does not guarantee you will see every record in the system. Pipedrive notes that even with export permissions, you can only export the data that’s visible to you based on your visibility group or item visibility, according to Pipedrive. Verify that your current visibility settings align with the revenue scope you need for the forecast meeting. See forecast categories.

To confirm the scope is correct before generating the file, review the filtered list in the interface. Check that the record count and the visible fields match your intended snapshot parameters. If the view excludes records you believe should be included, adjust your visibility group or item visibility settings first, then re-apply the filter. This verification step prevents saving a snapshot that is incomplete due to permission-based visibility constraints rather than filter logic.

When the filtered view displays the correct set of records, proceed to the export action. The resulting file will contain only the data visible under your current permissions and filters. If you need a broader scope for a different purpose, you must adjust your visibility settings or use a different account with appropriate permissions. Always treat the filtered view as the source of truth for the snapshot content.

Selecting the correct export option determines whether your snapshot captures the entire dataset or just the visible screen. In model-driven Power Apps, the system offers two distinct static worksheet modes that handle data scope differently. The "Static worksheet" option exports all the pages in the current view according to Microsoft. This ensures the file contains every record that matches the active filter, not just those currently rendered on the screen. Conversely, the "Static worksheet (Page only)" option exports the data from the current page only according to Microsoft. If you select this mode, the resulting file will miss records that exist on other pages of the same view. For a weekly pipeline review, choosing the page-only mode risks excluding deals that fall outside the immediate display, so verify which mode is active before initiating the download.

File format selection also affects how large datasets are handled. When exporting from HubSpot, the system may split the output into multiple files if the row count exceeds specific thresholds. Multiple files are expected when exporting CSV or XLSX files with more than 1,000,000 rows and XLS files with more than 65,535 rows according to HubSpot. If your pipeline snapshot approaches these limits, plan to combine or process several files rather than expecting a single consolidated document. Additionally, column counts are capped based on the file type chosen. For XLS and XLSX files, there's a limit to the number of columns that can be exported (256 for XLS and 16,384 for XLSX) according to HubSpot.

Recommendation: Select the "Static worksheet" mode in Power Apps to capture all pages, and choose XLSX over XLS in HubSpot if your field count exceeds 256 columns to avoid hitting the column limit.

When building a weekly pipeline snapshot, the scope of the export depends on how each system handles linked data and record relationships. In HubSpot, the export process downloads the current property values and associations for the selected records, according to HubSpot. This behavior applies to the specific records chosen for the export, capturing their existing relationship data at the time of the request.

In Pipedrive, activities, notes, and files linked to deals and contacts are not included in the primary deal or contact export. These items must be exported separately, according to Pipedrive. Use a separate pass to find deal attachments.

In Close, exporting opportunities from the leads page returns opportunities that belong to leads matching the given search criteria, according to Close. This mechanism ties the opportunity export to the lead-level search filters rather than applying a direct opportunity-level filter. The resulting file contains opportunities associated with the leads that meet the specified search parameters.

To maintain an accurate snapshot, define whether the analysis requires associated activities and notes. If the workflow relies on deal history or file attachments, plan for separate exports in systems that do not bundle these elements. For opportunity data, verify whether the search is applied at the lead level or the opportunity level to ensure the returned records match the intended scope.

Treat the download link, the export log, and rate limits as three separate concepts. The link gives you access to the file; the log tracks history; rate limits cap how many exports you can run. Do not confuse them.

In HubSpot, historical exports remain visible in your export log for 3 years, after which they are automatically removed, according to HubSpot. This retention period applies to the log entry, not the local file you saved. Your local copy does not depend on the log entry remaining visible.

HubSpot also limits export volume: you can complete up to 300 exports within a rolling 24-hour window, and up to three exports simultaneously, according to HubSpot. If you hit this ceiling, wait for the window to reset or reduce concurrent exports. These limits are specific to HubSpot’s “Export your records” feature and do not apply to other systems.

When you save the file, include the export date and the filter used in the filename. This practice helps you distinguish this week’s snapshot from last week’s if you archive multiple files. The snapshot is static; it does not update after download. If the pipeline changes after you export, the file reflects only the state at the moment of export. See close date change log.

You filter one view to 50 deals and 4 fields. On day 1 you export that view and save the file. You do not leave the file until day 7. At the review you still see those 50 deals. If 10 deals moved after the export, the file shows the earlier state.

Do this today: Open the filtered view for this week’s meeting, export it, and save the file on your computer with the export date and filter in the filename.

Which records will be included in the snapshot?

The included records depend on the specific page and search criteria used. In Close, exporting Opportunities from the leads page returns opportunities that belong to Leads matching the given search criteria, rather than acting as a direct opportunity-level filter according to Close.

Does page-only export include the whole pipeline?

No. In Microsoft, a static worksheet (Page only) exports the data from the current page only according to Microsoft. To include the entire view, select the static worksheet option, which exports all the pages in the current view according to Microsoft.

Will notes and activities be included?

In Pipedrive, activities, notes and files linked to deals and contacts must be exported separately according to Pipedrive. Do not assume these items appear in the primary deal or contact export.

When does the download link expire?

HubSpot download links to export files expire after 30 days according to HubSpot, and the Close link expires automatically after 7 days according to Close.