Custom object storage limits reached in territory management: How to archive old records without losing reporting accuracy?

klausdata
Sat, 14 Jun 2025 09:23:17 +0000

We’re hitting custom object storage limits in our territory management module and it’s blocking new territory assignments. Our sales ops team has been building out detailed territory hierarchies with custom objects to track regional performance metrics, competitive data, and market segmentation rules. We started getting errors last week when trying to create new territory records.

The error message shows:

Storage quota exceeded for custom objects
Current usage: 98.7% of allocated limit
Territory assignments suspended

I need to understand our options around custom object storage quotas and whether we can export historical data via API to free up space. We also need to maintain historical reporting integration for our quarterly reviews. Has anyone dealt with retention policy setup for territory data while keeping compliance requirements intact?