Skip to main content
Every visit a rep completes adds tasks, survey answers, photos, and often orders and ranging to your org. Over months and years, FieldKo data becomes one of the largest parts of your Salesforce storage. Use this page to see what grows fastest, check your storage, understand what FieldKo already limits, and plan retention and report performance before storage becomes a problem.

​
User Permissions Needed

​
What Grows Fastest

The following table lists FieldKo’s high-volume objects, from the usual fastest-growing down. The actual order depends on how many surveys, photos, and ranging checks your reps complete. For where each kind of data is stored, see Where FieldKo Stores Data and Where Photos Are Stored.

​
Data Storage and File Storage

Salesforce measures 2 kinds of storage:
  • Data storage holds records, such as visits, tasks, survey answers, and orders.
  • File storage holds attachments and Salesforce Files, which is where FieldKo photos go.
Photos usually drive file storage, and survey answers and ranging lines usually drive data storage. Your allocation depends on your edition and licenses. See Data and File Storage Allocations in Salesforce Help, and for your org’s allocation, check your Salesforce contract or ask your Salesforce account executive.

​
Check Your Storage

Review storage monthly, and after big rollouts:
  1. From Setup, in the Quick Find box, enter Storage Usage, and then select Storage Usage.
  2. Review the totals for data storage and file storage against your limits.
  3. In the list of record types, check how much each FieldKo object uses, and which users own the most storage.

​
What FieldKo Limits on Devices

FieldKo limits how much data each rep’s device downloads. These limits keep the app fast and sync short, but they don’t reduce storage in your org. Survey answer photos download from the start of last month.

​
Plan Retention and Archiving

Decide how long you need FieldKo data in Salesforce for day-to-day work and trend reports, and how long you must keep it at all. For example, you might keep the current and previous year in Salesforce for trend reports, and move older data to a data warehouse or archive. To archive older data:
  1. Agree on a retention policy with your business and compliance teams, for example by object and age.
  2. Export the records and photos you’re archiving, with their record IDs so you can join them later. See Export FieldKo Data and Photos.
  3. Check that the export is complete and readable in its destination.
  4. Delete the archived records with Data Loader, starting with child records: survey answers, then task surveys, then tasks, then visits.
  5. Empty the deleted records from the Recycle Bin, if your policy allows, to free the storage.
Deleted records are removed from reps’ devices at their next sync, and deleting photos removes them from Salesforce for good. Archive only records older than the sync date window, test your deletes in a sandbox, and keep your export until you’ve confirmed it’s complete.
For trend reports over long periods, consider reporting snapshots, which store summary results instead of every record. See Dashboard Running Users and Reporting Snapshots.

​
Keep Reports Fast on Large Data

Reports on survey answers, tasks, and visits slow down as the data grows. To keep them fast:
  • Always filter by date, such as the visit’s Planned Start or the record’s Created Date, and use relative ranges like Last 90 Days.
  • Filter on indexed fields where you can, such as record type, owner, lookup fields like Account or Visit, and your external ID fields.
  • Avoid “contains” filters on long text fields, such as a survey answer’s Answer or Question. Use numeric or picklist questions for the results you report on most. See Design Surveys and Tasks for Reporting.
  • Summarize in dashboards and snapshots instead of running detailed reports across years of data.

​
See Also

Last modified on October 20, 2026