Skip down to the research record

HubSpot offline cache: 50 records for each type, 200 total

Quota Forecast Editorial Team · Published · 11 min read

The HubSpot mobile app keeps your 50 most recently viewed records for each of four object types offline, up to 200 in total (HubSpot). This limit applies to each object type, meaning the app holds 50 records for contacts, 50 for companies, 50 for deals, and 50 for tickets.

This cache is strictly read-only. You can open and read the details of these 200 records when offline, but the app does not allow you to create new records or edit existing ones while disconnected. The scope of this offline access is limited to the four record types mentioned: contacts, companies, deals, and tickets. Other record types, such as files or custom objects, are not part of this offline cache. If a record was not among the 50 most recently viewed items in its specific category, it will not be available on your phone when you are offline.

This guide gives no equivalent cache figures for Freshsales, Pipedrive, Close, or Microsoft. The 50 and 200 limits above are HubSpot's. This difference matters when you are checking a deal before a call. If you rely on HubSpot, you know exactly which records are on your phone. If you use another tool, you must verify offline availability through that tool's specific documentation.

Key takeaways for mobile record cache before a sales check

  • The HubSpot mobile app stores your 50 most recently viewed records for each object type, including contacts, companies, deals, and tickets, according to HubSpot.
  • Plan any edits for when you are connected, since access is strictly read-only while you are offline, according to HubSpot.
  • Check that offline mode is on, because the system resyncs data automatically every 24 hours, according to HubSpot.

A filled reference table of the phone rule by publisher

HubSpot’s mobile app caches the 50 most recently viewed records for each object type across contacts, companies, deals, and tickets, allowing you to view up to 200 records when you are offline HubSpot. This guide gives no comparable offline cache size for the other publishers; their mobile rules cover form fields, save actions, sample text, or item-following rules instead.

PublisherPhone RuleSource
HubSpotCaches 50 most recently viewed records for each object type (contacts, companies, deals, tickets), up to 200 records total, in read-only mode offline. File properties, attachments, and custom objects are unavailable offline. You cannot edit, create, or delete records, properties, or activities while offline.HubSpot
FreshsalesThe mobile app displays the quick add fields configured in the web application in the Deals Module. Save the deal by clicking the tick icon on Android or the Save button on iOS at the top.Freshsales
MicrosoftSample deal topic line shown in the documentation: “125 CRM licenses for Contoso inc.” This guide gives no offline cache size for Microsoft.Microsoft
PipedriveThere are two ways to follow an item, depending on the type of item. This guide gives no offline cache size for Pipedrive.Pipedrive
CloseNo rule is listed for Close in this guide.—

Use this table to separate what the phone can show you from what it cannot. If a deal is missing from your phone screen, check whether it falls outside the 50-record window for its object type before assuming it is missing from the weekly total. For details on how forecast categories interact with the numbers you see on a phone, see Pipeline, Best Case, Commit: Forecast Categories Explained.

The 50 record cache, the 200 record total, and the 24 hour resync

Offline access must be turned on manually in mobile app settings before going offline, according to HubSpot. You must be connected to the internet in order to set up offline mode and in order to resync your offline data. When offline mode is turned on, the system automatically resyncs data every 24 hours. This refresh cycle applies to the cached records available on the device during that period.

Each cached record includes the three most recent engagements, and five upcoming tasks for each record. These activity snippets are stored alongside the core record data to provide context while the phone is offline. The resync process updates these stored details when the device reconnects to the internet.

To prepare for a mobile check, ensure the offline mode setting is enabled while you have a connection. This manual step is required before the phone can store the most recently viewed supported records for offline viewing. The 24-hour resync interval determines how frequently the stored data updates after the initial setup. If you plan to review a deal without internet access, confirm the setting is active and that the last resync occurred within the expected window.

The cache holds a limited set of records, and the resync timing ensures the data reflects recent changes. Check that your phone has completed a resync since the last time you made changes to the deal. If the data appears outdated, verify that the device was connected to the internet during the resync window.

Use the manual setup step to prepare offline access before you leave a connected environment, then confirm the records you need are accessible. According to HubSpot, accounts storing sensitive data are excluded from offline mode support. The 24-hour cycle is the standard refresh rate for the offline data. The activity snippets provide a snapshot of recent interactions and upcoming tasks for each record in the cache. Confirm the offline mode is on and that the last sync was recent before you rely on the phone for a sales check.

What you cannot change, open, or attach while the phone is offline

When the phone loses its connection, the mobile app shifts into a restricted state where the user can look at data but cannot modify it. According to HubSpot, access to CRM records is read-only in this mode. This means the revenue leader can view the deal amount and stage, but any attempt to type new information will not save. The interface remains visible, and the screen shows the data as it was last synced.

The restrictions extend beyond simple viewing. You cannot edit, create, or delete records, properties, or activities while offline. This block covers the entire range of standard sales actions. If a rep tries to update a close date or add a note to a deal, the app will not process the change. This limitation applies to all record types present in the cache, ensuring that the local copy remains unchanged until the next successful sync.

Certain data types are completely absent from the offline view. File properties and attachments are unavailable in offline mode. This means that PDFs, images, or other documents linked to a deal will not load on the phone. If a contract or proposal is attached to the record, that file is unavailable offline. This gap requires the leader to rely on the text fields of the deal record, such as the amount or description, rather than the supporting documents. To find a file on a connected device, see Find deal attachments: 4 publisher rules to check.

Custom objects are also unavailable in offline mode. If the organization uses custom data structures for specific deal attributes, those details will not appear on the phone. The cache focuses on standard record types, leaving out custom objects. This omission means that some contextual information might be missing from the mobile view. The leader should anticipate that the phone display is a subset of the full desktop record, specifically excluding these custom elements.

Freshsales fields on the phone form, and Microsoft's sample topic line

The mobile app displays the quick add fields that have been configured in the web application in the Deals Module, according to Freshsales. This means the phone form does not show every field in your system; it shows the specific quick add fields you set up on the web. If a field is not configured as a quick add field in the web application, it will not appear on the phone form. You can check your web configuration to see which fields are currently visible on the mobile device. This setup determines what data is available for quick entry when you are away from your desk.

To save a deal after entering data on the phone, click the tick icon on Android or the Save button on iOS on the top, as described by Freshsales. The save mechanism differs slightly between operating systems, but both actions commit the entered data to the record. Ensure you tap the correct control to finalize the entry. If you do not tap the save control, the data may not be committed to the system. This step is necessary to preserve the information you entered during the mobile check.

Microsoft provides a sample topic line for a new deal, showing "125 CRM licenses for Contoso inc." in its documentation, according to Microsoft. This example illustrates how a deal name might be structured in the system. It is a printed example of a deal topic, not a cache size or a specific record in your system. Use this format as a reference for how deal names appear in the interface. The example helps visualize the text that might be displayed when viewing a deal record.

Illustrative example: which deals stay on the phone

Suppose you view 50 deals, then 10 more. The cache keeps only the 50 most recently viewed, so the 10 earliest drop out and will not appear offline. Check the deal you need while you are connected.

A phone check for one live deal

Use this table to verify one specific software deal on your phone before the weekly call. The goal is to confirm which data points are visible in the current offline state. Pipedrive notes that there are two ways to follow an item, depending on the type of item, which helps distinguish how records are tracked compared with how they are cached locally.

FieldVisible on the phone?
ExampleAmount: yes or no; next step: yes or no

Note what you actually see on the device. If a field is blank or hidden, mark it as missing rather than assuming it is zero. Noting missing fields shows only what is visible on the phone, so compare the record with the connected version to tell whether it is incomplete. Do not attempt to edit the record during this check.

Write down whether the amount and the next step are visible. If either is missing, check the record on a connected device before assuming it is outside the offline set. Keep the check to one deal to avoid mixing up different pipeline items. The result tells you what you can discuss on the call without switching to a desktop view.

If the deal amount is visible but the next step is not, record that gap specifically. This helps you prepare a question for the rep about the activity log. Do not guess the missing data. The check is only about what is present on the phone right now.

Next step: if you use HubSpot, turn on offline access in its mobile app while you are connected, then run this check on one deal today. For a broader routine, see Check 8 data rules before the weekly sales call.

Mobile cache FAQ

Which deals are stored on the phone?

HubSpot stores the 50 most recently viewed deals for each object type on the device. This specific limit applies to the deals category within the mobile application's offline storage. The cache does not hold every deal in your pipeline, only the recent subset defined by that count.

Can I edit a deal while offline?

No, the application operates in read-only mode when the device lacks a network connection. Any attempt to modify data will be blocked until the phone reconnects to the internet.

How often does the phone copy refresh?

The phone copy refreshes automatically every 24 hours while offline mode is on.

Does every tool use the same cache?

No. Only HubSpot's cache figures appear in this guide. This guide gives no offline storage limits for the other tools. You must check each vendor's specific help documentation to understand their individual offline capabilities.

What do I check before the call?

Verify the deal is within the 50-record cache limit for its object type. Note any missing fields that might not have synced during the last 24-hour refresh. Confirm the amount and next step are visible on the screen before the meeting starts.

Sources