7 Ways Hospitality Leaders Are Managing Salesforce Data at Scale

Hospitality companies run some of the most data-intensive Salesforce environments in any industry. Guest profiles, booking histories, loyalty records, and service interactions accumulate across dozens of brands and hundreds of properties, all feeding into a CRM that customer care teams depend on every day. As Salesforce becomes more central to delivering differentiated guest experiences, the stakes around data protection, compliance, and operational continuity rise with it.

The following seven practices reflect how enterprise hospitality organizations are approaching Salesforce data management as their environments grow in scale and complexity.

1. Are you complying with GDPR without writing custom code?

For hospitality companies operating across Europe, or serving European guests from anywhere in the world, GDPR compliance in Salesforce is non-negotiable. What separates mature data management practices from reactive ones is how that compliance gets implemented.

Custom-coded solutions are common, but they create a fragile dependency: every time Salesforce releases an update or your data model changes, someone has to revisit the Apex classes keeping your compliance workflows intact. Leading hospitality organizations have moved toward point-and-click configuration for GDPR operations, including data deletion, transformation, and audit logging. This approach reduces the engineering burden, eliminates custom code maintenance, and makes compliance workflows auditable and repeatable across teams.

Accor Hotels, the largest hospitality company in Europe with 5,341 properties across 116 countries, took exactly this approach. When they expanded Salesforce to handle B2C operations for over 80 million guest accounts, the IT team needed a GDPR compliance workflow that didn't require building custom architecture. "Odaseva helps Accor avoid custom coding for GDPR because it's a point-and-click configuration," said Mathieu Gorju, IT Delivery Manager at Accor. "If we had chosen another solution, it would have been an Apex class we'd have to develop."

2. Does your backup strategy cover the objects your operations actually depend on?

Most hospitality companies using Salesforce for customer care rely on Knowledge articles: the internal documentation that agents reference when assisting guests with bookings, requests, and escalations. It's a critical operational asset, and it's also one of the trickiest to protect.

Restoring Salesforce Knowledge after a data loss incident requires specific handling that many backup providers either don't support at all or treat as an afterthought. The same applies to custom objects unique to hospitality data models; loyalty tiers, reservation structures, multi-brand account hierarchies that generic backup tools weren't designed to cover.

Enterprise hospitality organizations are raising the bar on what backup coverage actually means. Backing up standard objects and calling it done isn't sufficient when the objects your agents depend on most aren't included in the restore plan. The question to pressure-test your current backup approach: if you needed to restore everything from scratch tomorrow, what would be missing?

Accor's evaluation of backup providers surfaced early. Competitors didn't support Salesforce Knowledge, which was a hard requirement given how central Knowledge articles are to their call center operations. Full coverage across 2,100 objects, including Knowledge, was a prerequisite, not a nice-to-have.

Regulation is starting to formalize that expectation. The EU's NIS2 directive now requires covered organizations to prove, with documented evidence, that they can actually restore critical data after an incident; in travel that pulls in online travel agencies, booking platforms, and global distribution systems directly, and hotel groups through the partners they rely on. Backing up data is no longer the finish line; you have to show a restore works, which is what Odaseva's Restore Readiness Audits are built to evidence. 

3. How are you managing sandbox data ahead of each release?

Hospitality companies with large, complex Salesforce implementations release frequently, and each release introduces risk. Deploying to production without properly seeded sandboxes means testing against data that doesn't reflect real-world conditions, which is how bugs and performance issues slip through.

The manual alternative is time-consuming. Developer teams spend hours pulling records, anonymizing data, loading it into sandbox environments, and validating the results before a release can proceed. At scale, that overhead compounds across every sprint and every team touching the org.

The practice gaining traction among enterprise hospitality organizations is automated sandbox seeding: refreshing non-production environments with realistic, anonymized production data on a scheduled basis ahead of releases. This gives developers and QA teams accurate testing conditions while protecting guest data privacy, and it frees up engineering time that would otherwise go to manual data prep.

For Accor, Odaseva's Sandbox Seeding capability became a core part of their release management workflow. The ability to refresh sandboxes before each new release saved hours of developer time per cycle and eliminated the manual processes that had previously created bottlenecks across their teams.

4. What's your plan when data is accidentally deleted during a migration?

Data migrations are a routine part of managing an evolving Salesforce environment: new integrations, system consolidations, B2B-to-B2C expansions. They're also one of the highest-risk operations any admin team undertakes. Even carefully planned migrations produce incidents: records overwritten, relationships broken, data deleted by a process that ran broader than intended.

The difference between a migration incident that causes a disruption and one that gets quietly resolved comes down to recovery capability. Organizations with tested, complete backups can roll back to a known-good state and resume. Organizations relying on native Salesforce tools or generic backup providers often discover their restore options are more limited than expected, and the interruption that follows is measured in days, not hours.

Accor experienced this scenario directly. During a data migration, data was accidentally deleted. With a comprehensive backup in place, the team was able to restore to a previous state quickly, avoiding what Gorju described as a potentially highly disruptive incident. The ability to recover cleanly, rather than reconstruct manually, is what kept the incident from becoming a business continuity event.

5. Are you using API calls efficiently enough to back up at enterprise scale?

At the scale hospitality enterprises operate, tens of millions of guest accounts, billions of records, terabytes of files, API consumption becomes a real operational constraint. Backup processes that burn through Salesforce API limits create friction with other integrations and business processes running on the same org. In the worst cases, aggressive backup tools cause governor limit issues that affect production performance.

Sophisticated Salesforce data management at this scale requires careful optimization: intelligent use of Bulk API versus REST API depending on the operation, incremental backup strategies that avoid pulling full datasets unnecessarily, and PK chunking for large object extraction. These aren't just technical niceties; they're what separates enterprise-grade platforms from tools that work fine in smaller orgs but degrade at volume.

Accor's Salesforce environment spans 2.1 TB of data, 2.7 TB of files, and 1.1 billion records across 2,100 objects. Odaseva backs up that environment while consuming only 1.32% of available Bulk API calls and 0.16% of REST API calls, leaving the rest available for the business processes that depend on them.

6. Is historical guest data slowing your org down?

Hospitality organizations accumulate data faster than almost any other industry. Booking records, loyalty transactions, service cases, and guest interaction histories build up over years across multiple brands and geographies. Left unmanaged, that data volume degrades Salesforce performance: slower reports, sluggish searches, and everyday processes that frustrate agents and administrators alike.

Archiving is the practice of moving inactive or aged data out of active Salesforce storage while keeping it accessible when needed. Done well, it reduces org size, improves performance for users who need speed, and makes it easier to find and work with current records. Done poorly, or not at all, it creates a compounding performance problem that gets harder to solve the longer it goes unaddressed.

The scale at which this becomes critical is lower than most teams expect. Enterprise CRM environments processing high transaction volumes can accumulate billions of records within a few years of operation. One Odaseva customer in a high-volume industry reached 17 billion Salesforce records before implementing a structured archiving strategy; the performance impact on their org was significant enough that archiving became a business priority rather than a back-burner IT project. For hospitality companies managing multi-decade guest histories across global brand portfolios, the trajectory is similar. Odaseva's Data Archiving platform handles this at scale, using Salesforce Bulk and REST APIs efficiently, with PK chunking for large object extraction, and keeping archived data accessible through Salesforce-native integration rather than burying it in an external system your team can't easily reach.

7. Is your guest data ready for AI?

AI is reshaping how hospitality companies engage with guests: personalized recommendations, predictive service, automated loyalty management. Salesforce's Agentforce capabilities are accelerating this in the CRM context specifically. But AI performance depends entirely on the quality, completeness, and accessibility of the data feeding it.

Historical guest data locked in bloated orgs, incomplete because of gaps in backup coverage, or siloed across disconnected systems doesn't make AI smarter. It makes AI outputs less reliable. The hospitality organizations moving fastest on AI adoption are the ones that have already built a clean, well-governed data foundation: structured archiving policies that keep active data lean, backup coverage that ensures historical records are complete and restorable, and data management workflows that don't require engineering effort every time the data model changes.

The data readiness conversation is increasingly happening before AI implementation rather than after. Getting Salesforce data into a state where it can reliably power personalization and agentic workflows requires the same discipline as any other compliance or resilience initiative; it just carries a new set of business upside when it's done well. Odaseva's platform supports this by keeping Salesforce environments lean through archiving, maintaining complete historical records through comprehensive backup, and making data accessible across environments through tools like the Archiving Agent, which enables AI and users to query archived data directly. Odaseva's platform also keeps that data portable, replicating Salesforce records to the data and AI platforms teams build on, like Snowflake and Databricks, so historical and live records can power analytics and AI without loading the production org. 

The common thread across these seven practices is a shift from treating Salesforce data management as a background IT function to recognizing it as an operational foundation. Guest experiences depend on data that's accurate, recoverable, and compliant. As hospitality organizations scale their Salesforce environments, adding more brands, more geographies, and more B2C complexity, the cost of data management gaps scales with them.

For enterprise hospitality teams evaluating their current approach, Odaseva offers a purpose-built platform for exactly these environments. Request a demo to see how it handles the scale and complexity of your Salesforce org.