Export mechanisms in major CRM platforms
Understanding the export mechanisms available in your CRM is the first step toward monitoring them effectively.
In Salesforce, data can be exported via report downloads, list view exports, the Data Export wizard, Data Loader, the Bulk API, the SOQL API, and various third-party tools. Event Monitoring logs most of these events, but the logs are not always reviewed.
In Dynamics 365, exports occur via Excel export from views, the data export service, Power BI integration, the Dataverse connector, and direct API queries. The audit log tracks record access and modifications but does not always capture export volume explicitly.
In HubSpot, data can be exported via the contact export feature, list exports, custom reports, and the Contacts API. HubSpot's activity logs capture export events for some object types.
What normal export behavior looks like
Export monitoring is most effective when it is calibrated to individual users and roles rather than applied uniformly across an organization. A sales operations manager who produces weekly pipeline reports has a fundamentally different export baseline than a sales development representative who occasionally downloads their lead list.
Key dimensions to baseline per user include:
- Export frequency: How many export events does this user generate per day, week, and month?
- Record volume: How many records are typically included in each export?
- Object types: Which CRM objects does this user typically export?
- Timing: At what hours and on which days does this user typically export?
- Export mechanism: Which export methods does this user typically use?
High-risk export patterns
Patterns that deviate significantly from an established baseline, particularly in combination, warrant investigation:
- Export volume significantly above a user's historical average
- Export of object types the user has not previously exported
- Multiple exports of the same object within a short period (suggesting repeated extraction attempts)
- Export activity at hours inconsistent with the user's normal behavior
- Export immediately following a login from an unfamiliar location or device
- Export activity in the weeks immediately preceding known or suspected departure
- Bulk API queries returning unusually large result sets from a service account
Balancing security monitoring with business operations
Export monitoring should be designed to surface genuine risk for human review — not to block legitimate business activity. Effective implementation principles include:
- Alert on deviation from baselines, not on all exports above a fixed threshold
- Tier alerts by risk level — a single large export from a long-tenured user with a stable pattern is lower priority than a similar export from a new user or combined with other risk signals
- Design investigation workflows that can quickly determine whether a flagged export has a legitimate business explanation
- Review high-risk alerts promptly — time-to-detect matters when the exfiltration is in progress
Frequently Asked Questions
Can you prevent CRM data exports entirely?
Does Salesforce Event Monitoring capture all export types?
How quickly can unusual export behavior be detected?
What if a legitimate business activity looks like suspicious export behavior?
Are API-based exports harder to monitor than UI exports?
Related reading
Secure your CRM
CRMSentry provides continuous security monitoring, behavioral threat detection, and compliance posture management for Salesforce, Dynamics 365, and HubSpot.
Get a CRM Security Assessment