Salesforce Org Sizing

When sizing your Salesforce org, consider the following factors:

  • Object Storage: This is where Salesforce stores accounts, services, orders, tasks, cases and other records.
  • File Storage: This is where Salesforce stores file attachments (quote PDFs, order documents, case screenshots, etc.).
  • API Calls: These are inbound API calls (which are metered and limited) made by the Nextian Monitoring Integration as it updates elements and services: status, availability and performance metrics.
ImportantThe numbers below are approximate. Please contact us for a detailed estimation of your Salesforce org sizing.

Storage and API requirements will vary based on several factors, including:

  • Types of services
  • Total and monitored elements per service
  • Number of performance metrics
  • Number and frequency of change orders during service lifetime
  • Whether customer cases are stored in Salesforce or an external customer support system
  • Order and case comments volumes

Typical ballpark figures for based on the number of services (circuits, software subscriptions, etc.), look as follows:

ItemEstimate
Object Storage100K-0.5MB per service
File Storage1MB-2MB per service
API4K API calls per 10,000 monitored elements

Optimization Tip: Object and file storage can be significantly reduced by implementing a data retention policy to remove historical orders, inactive services, and closed cases past a certain age.

Was this page helpful?