--- sourceDocument: Australia Impact sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/impact Release : - australia ft:locale : - en-US ft:publication_title : - Australia Impact ft:clusterId : - ipact bundleId : - ipact --- # Impact storage estimation # Impact storage estimation {#ariaid-title1} * Release version: Australia * * Updated March 12, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Impact storage estimation The Impact Store app within ServiceNow stores data in your instance, affecting your instance's overall storage footprint. Storage usage depends on whether your instance is connected to the Impact Delivery Instance and on the level of collaboration activity with ServiceNow experts (squads). Unlike typical applications that generate data only locally, Impact facilitates ongoing collaboration that synchronizes additional data into your instance, increasing storage consumption. Show full answer Show less ## Storage Behavior Based on Connection * **Not connected to Impact Delivery Instance:** Data is generated solely within your instance, such as health scan reports. Storage usage grows proportionally with feature use, similar to other ServiceNow applications. * **Connected to Impact Delivery Instance:** Data is initially migrated and then synchronized periodically to support collaboration. This includes outcomes tracked jointly, Product Adoption Roadmaps (PARs), Accelerator requests and updates, conversations, attachments, and artifacts shared by squads. This collaboration leads to incremental storage growth based on activity levels. ## Factors Driving Storage Growth Storage consumption primarily depends on: * Number of tracked outcomes * Number of Product Adoption Roadmaps * Volume and frequency of Accelerator requests and updates * Frequency of conversations and collaboration * Use and size of attachments and supporting documents, which typically contribute most to growth * Data retention duration influenced by cleanup and archiving policies ## Estimated Storage Ranges Storage needs vary based on usage tiers as follows: * **Small (light usage):** Limited outcomes (5--10), few PARs, minimal Accelerator activity, low collaboration, less than 0.5 GB storage. * **Medium (moderate usage):** Moderate outcomes (11--25), multiple PARs, regular Accelerator updates, moderate attachments, ongoing collaboration, 0.5 GB to 10 GB storage. * **Large (high usage/mature adoption):** High outcomes (25+), extensive PARs, frequent Accelerator use, significant attachments including large files, continuous collaboration, storage over 10 GB. ## Key Considerations for ServiceNow Customers Impact data resides within your ServiceNow instance and contributes to overall database storage usage. Storage growth correlates directly with feature usage and collaboration levels. Customers with higher engagement in Impact's capabilities should anticipate increased storage consumption and plan accordingly for capacity management. The Impact store app stores data within your ServiceNow instance and contributes to your instance's overall storage footprint. Storage usage varies depending on whether your instance is connected to the Impact Delivery Instance and on the level of collaboration activity. ## Why Impact storage may differ from other applications {#impact-store-app-storage-estimation__why-impact-storage-differs} Unlike most applications that generate data only within your instance, Impact enables ongoing collaboration between your organization and ServiceNow experts (squads). When connected to the Impact Delivery Instance, this collaboration migrates and synchronizes additional data into your instance, increasing its storage footprint beyond what is generated locally. ## How storage usage changes based on connection {#impact-store-app-storage-estimation__storage-by-connection-state} Storage behavior differs depending on whether your instance is connected to the Impact Delivery Instance. Not connected to the Impact Delivery Instance : Data is generated only within your instance. For example, running health scans produces reports and findings that consume storage. The storage footprint scales proportionally with feature usage, where more health scans or more generated records result in more storage consumption, similar to other ServiceNow applications. Connected to the Impact Delivery Instance : Data is initially migrated and then periodically synchronized, enabling collaboration between your organization and your Impact squads. Additional data is introduced into your instance, including: * Outcomes defined and tracked jointly * Product Adoption Roadmaps (PARs) created by the Squad * Accelerator requests and execution updates * Conversations and collaboration records * Attachments and supporting artifacts shared by the Squad This results in an incremental increase in storage usage based on the level of collaboration and activity. ## What drives storage growth {#impact-store-app-storage-estimation__what-drives-storage-growth} Storage usage in Impact is primarily driven by the following factors: * Number of outcomes being tracked * Number of Product Adoption Roadmaps (PARs) * Volume of Accelerator requests and updates * Frequency of conversations and collaboration * Use and size of attachments and supporting documents, which typically contribute the most to storage growth * Duration of data retention, effected by cleanup and archiving rules ## Illustrative storage footprint ranges {#impact-store-app-storage-estimation__storage-footprint-ranges} The following ranges are indicative examples to help estimate potential storage usage based on typical usage patterns. Actual values may vary based on implementation and usage. {#impact-store-app-storage-estimation__table-storage-ranges__entry__3} | Usage tier | Typical characteristics | Estimated storage impact | |-|-|-| | Small (light usage) | * Limited outcomes (for example, 5--10) * Few Product Adoption Roadmaps * Minimal Accelerator activity * Limited or no attachments * Low collaboration volume | Less than 0.5 GB | | Medium (moderate usage) | * Moderate outcomes (for example, 11--25) * Multiple Product Adoption Roadmaps * Regular Accelerator requests and updates * Moderate use of attachments * Ongoing collaboration and conversations | 0.5 GB- 10 GB | | Large (high usage / mature adoption) | * High number of outcomes (for example, 25+ across teams) * Extensive Product Adoption Roadmaps * Frequent Accelerator usage * Significant volume of attachments and artifacts, including large PPTs and images * Continuous collaboration with ServiceNow squads | 10 GB+ | [Table 1. Estimated storage ranges by usage tier] {#impact-store-app-storage-estimation__table-storage-ranges} ## Key considerations {#impact-store-app-storage-estimation__key-considerations} * Impact data is stored within your instance and contributes to overall database storage usage. * Storage growth is directly correlated with feature usage and collaboration levels. * Higher engagement with Impact capabilities may result in increased storage consumption.