ELLE01EFFE02Services03Events04Blog05Company06Careers07
← All articles
Legal · ELLEOctober 27, 20264 min read

Moving matter data to the cloud: a checklist for Swiss law firms

The questions to settle before client files leave your own servers: data residency, professional secrecy, access, audit trails, AI providers and an exit plan.

Written with AI and reviewed by the Logol team.

For many Swiss law firms, the cloud is no longer an unusual step. Email and documents often run on cloud services already. The question is rarely whether to move, but how: with which provider, under which conditions and with which safeguards. Matter data is not ordinary business data. It is covered by professional secrecy, often contains sensitive personal data, and it is the reason clients trust the firm.

This checklist is written for managing partners and COOs preparing that decision. It does not replace legal advice. What applies to your firm depends on your clients, your practice areas and your professional rules, so review the result with your own counsel or data protection officer.

Before anything else, map what you are moving: matters, client master data, documents, emails, time and billing records, conflict data and KYC files. Know which system holds what today. A migration is also the right moment to decide what not to move.

Where the data is stored

Data residency and the legal framework

  • Where is data stored, including backups and replicas? Where is it processed?
  • Which entities of the provider can access it, from which countries, and in which situations, for example support cases?
  • Does the contract reflect the Federal Act on Data Protection (FADP) and, where relevant, the GDPR?
  • Is there a data processing agreement that lists subprocessors and requires notice before they change?

Whichever region you choose, make sure it covers storage and backups, not only the primary data centre.

Professional secrecy

Art. 321 of the Swiss Criminal Code protects what clients entrust to their lawyers. When a provider is involved, the firm remains responsible for that protection. In practice, firms usually look at:

  • Contractual confidentiality obligations for the provider and its staff, ideally with explicit reference to professional secrecy.
  • Encryption in transit and at rest, and who holds the keys.
  • Clear rules on how access requests from authorities or third parties are handled, and how the firm is informed.
  • Guidance from your bar association, where available.

Who can see it

Access control

  • Multi-factor authentication for every user, with no exceptions for partners.
  • Role-based access: who can see which matters, including information barriers for sensitive files.
  • Prompt removal of access when people leave the firm or change teams.
  • A regular review of who has access to what, with a named owner.

Audit trails

  • Logs that show who opened, changed, exported or deleted what, and when.
  • Logs the firm can actually read and search, not only the provider.
  • A defined retention period for those logs.
  • Independent certification of the provider, such as ISO/IEC 27001, and a clear view of what the certificate covers.

What AI does with it

Most cloud platforms now come with AI features. They raise their own questions, and they deserve answers in writing.

  • Which AI models are used, and where are prompts and outputs processed?
  • Is client data used to train or improve models? Insist on a clear answer, stated in the contract.
  • Are prompts and outputs stored, for how long, and by whom?
  • Does the AI respect the same access rights as the user? A search should never return documents from a matter the user cannot open.
  • Can the firm switch AI features off, per user or per type of data?
  • Are AI outputs traceable, so a lawyer can see what a suggestion is based on?
  • Who approves what the AI proposes? An AI that drafts is useful. An AI that sends, books or decides without a person is a different matter.

How you get it back

The best time to plan the exit is before you sign. It is also a good test of the provider.

  • Can you export all data, including documents, metadata, time records and audit logs, in a usable format?
  • How long is data kept after the contract ends, and how is deletion confirmed?
  • What support is available during a migration, and on what terms?
  • Is your own archiving obligation covered for files that must be kept for years after a matter closes?
  • Have you tested an export at least once, with real data?

A provider that answers these questions calmly and in detail is usually a provider you can work with. One that avoids them tells you something too.

In summary

Few firms answer every point on day one. What matters is that each point has an owner, a written answer and a date for review. Keep the checklist with the contract, and revisit it when the provider adds features, especially AI features.

At Logol, we work through these same questions with firms that move to ELLE, our integrated CRM, ERP and DMS for law firms. Because clients, cases, conflict checks, time, billing, accounting, documents and email sit on one platform and one data model, there is one system to secure, audit and export instead of several. ELLE runs in the firm's own Microsoft tenant, in its region. Logol is certified to ISO/IEC 27001:2022, and the platform uses encryption, multi-factor authentication, role-based access and full audit trails. Its AI proposes, and lawyers confirm. We recommend asking every provider the same questions, including us.

Would you like to see it applied to your processes?

Thirty minutes with our team: we start from your situation, not from a presentation.