Bringing your CRM into line with the revised Swiss data protection law is not rocket science. You do not need to be a lawyer or an IT specialist: in 30 minutes, you can check whether your tool is compliant or whether it leaves you exposed. This guide shows you how, without the jargon.
In short: a CRM that complies with the revised FADP is a tool where you know where your data is stored and who can access it, and that lets you export or permanently delete that data. Here are the 8 points to check and how to verify them yourself in 30 minutes.
Why worry about it now? Since 2026, the transition period of the revised Federal Act on Data Protection (FADP) has ended. In practical terms, for your SME, a complaint from an unhappy customer can now lead to a very real fine of up to CHF 250,000, imposed under the oversight of the FDPIC (the Federal Data Protection and Information Commissioner, the Swiss authority that ensures the law is respected). And a fact that is often overlooked: the fine targets the person who makes the decisions, not the company.
Your CRM is on the front line, because it holds your most sensitive asset: your customer data. Names, email addresses, phone numbers, purchase history, sales notes. Which raises a first, very simple question: do you know in which country this data is stored, and who can legally access it?
If the answer is not obvious, this guide is for you. Together, we will look at what the law really expects from your CRM, how to audit it in 30 minutes, and what compliance costs.
What does the revised FADP change for your CRM?
The FADP applies to every Swiss organisation that processes personal data. Personal data is any information that identifies an individual: name, email address, phone number, job title, purchase history, sales notes. By definition, your CRM contains it.
The law rests on a few common-sense principles:
- A legitimate reason for collecting the data
- The bare minimum: you collect no more than you need
- Transparency: the person knows you are processing their data
- Faithful use: the data serves only the purpose that was announced
- Accurate data, kept up to date
- Security: concrete measures protect the data
- Caution abroad: any transfer outside Switzerland requires safeguards
Compared with the old law, there are four concrete changes:
- You must provide better information: your privacy page must state who receives the data and whether it is sent abroad
- The record of processing activities is only mandatory from 250 employees (most SMEs are exempt)
- A data breach must be reported to the FDPIC promptly
- Fines are personal: up to CHF 250,000 for the person responsible, not for the company
Key takeaway: the FADP penalises the person who decides, not the company. Whoever chooses the CRM, whether CEO, CFO or IT manager, is personally liable.
Where is your CRM data stored (and why does it matter so much)?
The answer to this question determines most of your risk. Yet many SME managers would be unable to say in which country their CRM actually stores their data.
The CRMs used by Swiss SMEs fall into 3 categories:
| Category | Examples | FADP status |
|---|---|---|
| US cloud | HubSpot, Salesforce, Zoho, Pipedrive | Subject to the Cloud Act and the Swiss-US DPF |
| European (EU) cloud | OVHcloud, Hetzner, Microsoft Azure EU | EU recognised as adequate by the Federal Council |
| Swiss cloud | Solutions hosted by Infomaniak, Exoscale, Swisscom | Directly subject to Swiss law |
The FDPIC recommends favouring hosting in Switzerland or in a country offering protection deemed adequate by the Federal Council. The United States does not enjoy this recognition unconditionally. Its status depends on the Swiss-US Data Privacy Framework (see next section).
The issue is not only geographical. If your data is stored with a provider subject to US law, that provider may be compelled to hand it over to foreign authorities, even if the servers are located in Europe.
Why does a US CRM raise questions under the FADP?
The problem is not the quality of the software. HubSpot and Salesforce are well-established CRMs. The question is a legal one, and it comes down to three frameworks: the Cloud Act, the EU-US DPF and the Swiss-US DPF.
The Cloud Act is a US law dating from 2018. It allows US authorities to demand data held by a US company, wherever it is stored in the world. In other words: even if your data sits on a server in Europe, if your provider is a US company, the US courts can theoretically access it.
To allow data exchanges nonetheless, two agreements exist: one between the European Union and the United States (since 2023), and its equivalent between Switzerland and the United States (recognised by the Federal Council in 2024). They allow a certified US company to receive European or Swiss data.
The catch: the robustness of these agreements is disputed. A previous agreement has already been struck down by the European courts, and several lawyers expect the current framework to suffer the same fate, a scenario they have already nicknamed "Schrems III". Nothing has been decided so far, but the risk is real: if the European agreement were to fall, Switzerland would review its own in short order.
For a Swiss SME, legal uncertainty is a risk in itself: a transfer that is considered lawful today might no longer be so tomorrow.
Note: anticipating these developments lets you stay in control of your compliance timetable rather than being forced into an emergency migration.
We will soon publish a dedicated article with a detailed analysis by provider.
What are the 8 FADP requirements for your CRM?
Here are the 8 boxes a CRM must tick to be compliant. For each one, what it means in practice, without the legalese.
1. A signed data processing agreement
You must have a contract with your CRM provider that specifies what it is allowed to do with your data: for what purpose, for how long, which data, and with which security measures. It may not entrust the data to another provider without your written consent.
Without this contract, your provider is simply not entitled to process your data.
2. Verifiable hosting
Your provider must be able to tell you clearly where your data is stored: in which country, and with which guarantees (for example a recognised security certification such as the ISO 27001 standard). This information should be easy to obtain, not available only through a paid audit.
3. Strong encryption
Your data must be protected at two points: when it is stored, and when it travels over the internet. These protections have technical names (AES-256, TLS 1.3), but you only need to check one thing: that your provider confirms it encrypts your data in both cases. This is now a basic standard.
4. Role-based access
Each employee should only see the data they need for their work. A good CRM lets you define roles (who sees what) and, ideally, keeps a log of who viewed or exported what.
5. Truly permanent deletion
When data is no longer needed, or when a person legitimately asks for it to be removed, it must genuinely disappear. Not simply switch to "deactivated" status while remaining in the database and the backups.
6. A record of consent
For prospecting (emails, calls), you must be able to prove that the person agreed to be contacted: when, how and on what basis. And if you import contacts, this history must come with them.
7. Data export on request
Anyone can ask you for a copy of their data. Your CRM must let you export it easily, in a readable format (an Excel or CSV file), without having to go through the provider's technical support.
8. An alert in case of a breach
If your provider suffers a security breach, your contract must require it to notify you quickly. Quickly enough for you, in turn, to alert the FDPIC, as the law requires.
How can you audit your CRM in 30 minutes?
- 1
Identify the hosting country
3 minLook in the official documentation or the data processing agreement for the country and location where data is stored. Write down the answer.
- 2
Retrieve the data processing agreement
2 minCheck whether you have a signed data processing agreement (often called a "DPA" by providers). If you cannot find it, mark it as missing.
- 3
Test deleting a contact
4 minCreate a test contact, then delete it permanently. Check that it disappears from all views, exports and accessible backups.
- 4
Test a full export of a contact
3 minExport all the data for one contact into a single file. Check the format, completeness (custom fields, attachments, history) and the time it takes.
- 5
Check roles and permissions
4 minList the available roles. Check that a standard user cannot access other teams' data or export the entire database.
- 6
Look for the consent history
3 minFor 5 recently imported contacts, check whether consent is documented (date, source, method). If the information is missing, mark it as missing.
- 7
Check the encryption
2 minRead the security documentation. Look for an explicit mention of AES-256 at rest and TLS 1.3 in transit.
- 8
Read the breach notification clause
3 minIn the data processing agreement, find the clause on notification in the event of a breach. Write down the deadline it sets.
- 9
Check your privacy notice
3 minDoes your website mention the CRM you use, its hosting country and any transfers abroad? If not, you are not meeting your duty to inform.
- 10
List the sub-processors
3 minAsk the provider for the list of its sub-processors and their countries. Each sub-processor is a potential transfer that needs to be documented.
What is your score?
| Positive answers | Compliance level |
|---|---|
| 8-10 YES | Good level. Keep monitoring. |
| 5-7 YES | Moderate risk. Prioritise the missing points. |
| 0-4 YES | High risk. Compliance work is urgent. |
What should you do if your CRM falls short?
Three approaches, in increasing order of investment:
Option 1: bring your current tool into compliance
Suitable if the gaps are mainly administrative (missing data processing agreement, incomplete privacy page, poorly configured roles). Request the agreement from your provider, update your documents and adjust the permissions.
Option 2: strengthen your current tool technically
If the CRM is hosted in Switzerland or the EU but lacks features (consent not logged, incomplete deletion), activate the available modules or ask the provider for the improvements.
Option 3: migrate to a better-suited CRM
Worth considering if the CRM is hosted in the United States with no credible answer to the legal risks, or if the tool structurally cannot achieve compliance (deletion impossible, no consent tracking).
How much does an FADP-aligned CRM cost?
A comparison of the four CRM profiles available to Swiss SMEs in 2026:
| CRM type | Price per user/month | Native FADP compliance |
|---|---|---|
| Swiss-hosted CRM | CHF 29-89 | Yes (depending on provider) |
| European (EU) CRM | CHF 25-150 | Depends on configuration |
| US CRM | USD 25-300 | No, requires agreement + risk assessment + protection clauses |
| Self-hosted open-source CRM | CHF 0 + infrastructure | Depends on your infrastructure |
For an SME with 10 users, a Swiss-hosted CRM represents an annual budget of CHF 3,500 to 10,000. Compare this with the potential fine of CHF 250,000 and the cost of proceedings before the FDPIC (which can last several months and generate legal fees).
What do Swiss SMEs ask us most often?
Does the FADP apply to my SME with 5 employees?
Yes. For most of its obligations (security, information, data subjects' rights, data processing agreements), the FADP makes no distinction based on size. The only exception: the record of processing activities, which is mandatory only from 250 employees.
What does an SME actually risk in the event of non-compliance?
Three risks: a personal fine of up to CHF 250,000; a complaint from a customer or employee to the FDPIC that may result in the processing being suspended; and a commercial risk, as large Swiss accounts increasingly demand proof of FADP compliance.
Are Swiss CRMs automatically compliant?
No. Hosting in Switzerland is an advantage, but compliance also depends on features: effective deletion, consent management, access control, portability, encryption and contractually agreed breach notification.
Can I keep using HubSpot or Salesforce with standard contractual clauses?
It is possible, under four conditions: a signed data processing agreement, a documented assessment of the risks linked to this transfer to the United States, protection clauses annexed to the contract, and explicit information in your privacy notice. It is up to you to prove that everything is in order.
Does the FADP concern me if nobody has asked me about it yet?
Yes, absolutely. The law applies as soon as you process data, regardless of what your customers ask. The absence of requests today says nothing about tomorrow: compliance is becoming a criterion in Swiss B2B tenders.
How long does it take to become compliant?
For an SME with 10-30 employees, allow 2 to 4 weeks of work spread over 2-3 months. Data processing agreement and legal documents: 1 week. Audit and configuration: 2 weeks. Privacy page and training: 1 week. A full migration adds 4-8 weeks.
Do I need to declare my CRM to the FDPIC?
No. The record of processing activities is only mandatory for companies with 250 or more employees. Documenting your processing internally remains good practice, but you only need to notify the FDPIC in the event of a data breach.
What is the first thing to do today?
Three actions: 1) audit your CRM with the 10-step checklist above, 2) ask your provider for the data processing agreement by email (keep a record), 3) update your privacy page to mention the CRM you use and its hosting country. Cost: zero francs. Impact: immediate.
Can FADP compliance become a competitive advantage?
SMEs that take compliance seriously are one step ahead. They can respond to tenders that require FADP guarantees. They reassure their customers. They protect their managers from personal fines that far exceed the cost of becoming compliant.
In 2026, an FADP-aligned CRM is not a luxury. It is the new norm.
This article is based on the official sources available as of May 2026. The legal framework is evolving; we update it every 6 months.
Official sources:
- Official FDPIC website
- Full text of the FADP (SR 235.1)
- Data Protection Ordinance (DPO, SR 235.11)
- Transferring data abroad (FDPIC information)
- Text of the US Cloud Act (H.R. 4943)
Need help? To audit your CRM or compare Swiss solutions, contact us. A free 30-minute audit to assess your compliance and identify priority actions.
