Skip to content

Kit Gratos

Web resources

IT Platforms: How to Tell the Different Types Apart and Choose the Right Solution?

When migrating a business service from one cloud platform to another, the first obstacle isn’t technical: it’s exporting the data. Formats…

Ingénieur informaticien analysant différentes plateformes logicielles sur plusieurs écrans dans un bureau moderne

When migrating a business service from one cloud platform to another, the first obstacle isn’t technical: it’s exporting the data. Proprietary formats, dependencies on specific APIs, and the cost of rebuilding on the target platform all mean that choosing an IT platform is as much about how easily you can leave as it is about the features it offers.

The European Data Act, which sets out requirements to make switching providers easier (data exports, switching assistance, and measures to ensure functional equivalence for IaaS services), confirms that reversibility has become a selection criterion in its own right.

Exit test before committing: checking a platform’s reversibility

Before signing an annual contract or deploying a first project, you can run what’s known as an exit test. The idea is to simulate a complete migration and measure what switching providers would actually cost.

An exit test covers three distinct operations. First, a raw data export: does the platform let you retrieve all your data in a standard format (CSV, JSON, SQL), or does it require a proprietary format that will need to be converted?

Next, rebuilding the service: how long will it take to recreate workflows, automations, or integrations in another environment? Finally, checking for hidden dependencies—connectors, plugins, and provider-specific modules that won’t work elsewhere.

The Data Act aims to eliminate fees charged by providers for switching services. However, the organization remains responsible for its internal migration costs: adapting applications, running test campaigns, and setting up the target environment. Regulatory portability does not guarantee a simple or inexpensive migration.

To better understand the different types of IT platforms, it’s worth evaluating them in terms of reversibility rather than simply comparing feature lists.

Technician in a server room comparing cloud and on-premises infrastructure solutions on a tablet

Cloud, on-premises, and hybrid platforms: operational selection criteria

Platforms are generally divided into three broad categories based on their hosting model. Each category comes with different constraints around portability, security, and data control.

Cloud platform (SaaS, PaaS, IaaS)

Cloud platforms come in three tiers. SaaS (software as a service) provides a ready-to-use application: you use it without installing anything. PaaS (platform as a service) provides a development and deployment environment. IaaS (infrastructure as a service) provides virtual machines, storage, and networking.

The closer you get to the infrastructure layer, the more control you retain over the architecture—but the more complex it becomes to rebuild if you migrate. A SaaS service is easier to replace than a customized IaaS environment.

On-premises platform

On-premises hosting remains a good option when data must stay within a defined physical perimeter or when network latency is a critical constraint. The trade-off is that hardware maintenance and security updates are entirely the responsibility of the internal team.

Hybrid architecture

A hybrid setup combines cloud and on-premises environments. Sensitive data stays on-site while less critical services are deployed in the cloud. However, this configuration makes it harder to map dependencies during an exit test, since data flows between two separate environments.

Security and NIS2 compliance: a selection filter for affected businesses

Cybersecurity is no longer a secondary consideration when choosing a platform. The French bill transposing the European NIS2 Directive was adopted by the National Assembly on November 17, 2026. The bill introduces new requirements for risk management, securing subcontractors, and incident reporting for the entities it covers.

For organizations covered by this framework, comparing platforms now means asking specific questions:

  • Access traceability: Does the platform provide usable audit logs with timestamps and user identification, including for access by the provider’s subcontractors?
  • Notification commitments: In the event of a security incident, how quickly does the provider commit to notifying its customers, and is this commitment contractual or merely indicative?
  • Subcontracting chain: Does the provider document all of its own service providers with access to the data or infrastructure, and under which jurisdiction do they operate?

The transposition of NIS2 into French law has followed a turbulent parliamentary timeline. The requirements that actually apply may vary depending on the bill’s stage of adoption and the implementing decrees. Checking the current state of the law before requiring a provider to comply with NIS2 is a sensible precaution.

Team of professionals meeting to choose the right IT platform for their needs

A practical comparison checklist for choosing a platform

Rather than building an exhaustive matrix, you can focus your evaluation on five points that quickly reveal whether a platform is suitable for a given use case.

Criterion What to check
Export format Data can be retrieved in an open format (CSV, JSON, SQL) at no extra cost
Proprietary dependencies Number of connectors or plugins that only work on this platform
Rebuilding costs Estimated time to recreate an equivalent service with another provider
Security commitments Audit logs, notification timelines, subcontracting documentation
Scalability Ability to add users or features without changing plans

This checklist works just as well for a web platform aimed at end users as it does for a marketing automation tool or a mobile development environment. The goal is to make the choice reversible, not just functional at the time of signing.

One final point that’s often overlooked: test the data export using a real, even if limited, dataset before going live. The formats described in the documentation don’t always match what the platform actually produces. A few hours spent checking can save weeks of cleanup later.

IT Platforms: How to Tell the Different Types Apart and Choose the Right Solution?