Switching company
Tell us where your data is and where it needs to go.
Choose your roleCLOUD SWITCHING AS A SERVICE
Switch systems.
Keep your data.
Switona guides moves between applications, platforms and your own infrastructure. Companies and providers share one guided case: verify authority, prepare data and explicitly authorize the transfer.
Create an account. Verify the company. Explicitly approve.
YOUR DATA. YOUR NEXT MOVE.SW / 01
01 / Source
Applications & platforms
Databases & storage
Cloud & on-premises
switonaOne neutral switching layerMap → Transform
02 / Destination
New application
New cloud
Own infrastructure
Your current environment
Analyse Understand Map Transform Validate Transfer
Your next environmentMade in Germany. Built for Europe.Company authorization requiredFiles & REST APIsDatabase in Frankfurt
Move your data safely
One switching layer for everyone involved.
Current software provider
Provide the source. Switona handles the handover.
Choose your roleNew software provider
Tell us how you need the data. Switona prepares it accordingly.
Choose your roleCLOUD SWITCHING, ACROSS YOUR STACK
More than a software switch.
Switona is designed for data portability across cloud services, platforms and your own infrastructure. SaaS is one use case alongside databases, storage, infrastructure and platform services.
IaaS / PaaS
Cloud & platforms
Data and portable artifacts across compatible environments.
DBaaS
Databases
Prepare schemas, tables and relationships for a new destination.
STORAGE
Files & objects
File collections, object metadata and traceable transfers.
SaaS / APPS
Business applications
ERP, CRM and custom software, with their business history.
Cloud → CloudCloud → On-premisesOn-premises → CloudHybrid & edge
Technical scope is evaluated for each source and destination. Data transfer alone does not provision infrastructure or guarantee functional equivalence or uninterrupted workload migration.
YOUR INFRASTRUCTURE. YOUR DECISION.
Your data should open doors.
Not close them.
A change should not get stuck on data formats, dependencies or vendor lock-in. From business applications and databases to storage and cloud services, Switona turns different exports into a migration process you can review.
Understand the scope
Consider records, files, metadata and portable artifacts together with their dependencies.
Stay in control
Review mappings, resolve warnings and approve before anything moves.
Move on your terms
Choose your next platform without rebuilding migration infrastructure.
FROM LEGACY TO NEXT
A clear path for every move.
One guided case with mandatory approvals. Each step explains what to do next.
01
Create a case
Define the company, current system, destination and data scope. Companies or providers can initiate.
02
Obtain company authorization
Switona checks authority. The verified contact receives an email, signs digitally, and Switona performs a final review.
03
Set up source and destination
Provide supported files or select a verified REST connection. Data access remains locked until company authorization.
04
Review mappings
Define fields, types, relationships and exclusions. Mapping decisions are saved for review.
05
Check the simulation
Inspect the preview and error report. Resolve blocking findings before execution.
06
Confirm cost and transfer
Explicitly approve the payer and exact transfer. Relevant changes require fresh approvals.
07
Transfer and document
Generate an import package or deliver through a connected API. Verify the outcome and delete temporary files after the selected period.
CLEAR RESPONSIBILITIES. EXPLICIT APPROVALS.
You stay in control of your data.
An account lets you get started. It does not automatically grant access to company data. Every switch follows the same protected process.
No approval, no data access. No second approval, no transfer.
Verify the company
Independent verification, a digital mandate and final review before the first upload.
Explicitly approve the switch
A separate approval binds the transfer to the prepared data, participants and destination.
ONE LAYER. ANY DIRECTION.
Many systems. One common language.
One control layer, with rules appropriate to each data type. Structured data uses a normalized model. Files, objects and portable artifacts use transfer manifests and integrity checks. Source and destination adapters remain reusable.
EXAMPLE: FIELD MAPPING FOR APPLICATION DATA
SOURCE SCHEMA
Legacy ERP 01
customer_nostringcompanystringemailstring
Universal Data LayerCustomer ID
Company Name
Email
NORMALIZED MODEL
TARGET SCHEMA
New business application02
customerIdstringorganizationNamestringemailAddressstringONE USE CASE, IN DETAIL
Complex migrations. A remarkably clear view.
This ERP migration illustrates one workflow: mappings, warnings and records in one place. Database, storage and infrastructure moves each need their own validation criteria.
Migration workspaceERP migrationDEMO WORKSPACE
MIG-2026-0042
Microsoft Dynamics → New ERP
Records detected80,053
Mapping confidence96%▁▂▃▅▆█
Warnings to review207
| Data entity | Validation progress | Status |
|---|---|---|
| Customers | 12,402 / 12,402 | Validated |
| Invoices | 48,223 / 48,223 | Validated |
| Documents | 19,221 / 19,428 | Review needed |
Ready for your approval207 documents need attention before transfer.
Illustrative product preview. No live connection.eu-central · TLS
THERE'S MORE THAN ONE WAY IN
No connector? No dead end.
API, database export, file archive or object manifest: the path depends on your environment. We evaluate exportability, formats, dependencies and target compatibility before a migration.
REST connection
Configure and test an HTTPS API with authentication, source fields and destination requirements before use.
Test a connection
File import
CSV/TSV, XLSX, JSON, JSONL/NDJSON, flat XML and ZIP packages containing supported files. Content and limits are checked on import.
Bring an export
Specialist adapter
GraphQL, SFTP, native database dumps and proprietary formats require a separate adapter. Availability and scope are agreed first.
Review requirements
INTELLIGENCE WITH GUARDRAILS
Automatic suggestions. Deliberate approval.
Switona identifies field names, data types and relationships using deterministic semantic rules. You review mappings before execution. No external AI service is currently connected, and migration data is not used to train models.
Rules suggestExample
CustomerNocustomer_idYou approveHuman-approved mapping
source.CustomerNo → target.customer_idEnterprise IT
Built for the people behind the systems.
Your IT team should be able to plan repeatable moves across applications, databases, storage and cloud environments. Switona brings data preparation, validation and technical handovers into one neutral migration layer.
- Repeatable mappings and reusable connectors
- Validation and previews before import
- Centralized history and an audit trail
For providers
Make switching to your services easier.
For cloud, platform, storage and software providers: use reusable export and import paths for customer onboarding and technical exit workflows.
- Reusable source and destination adapters
- API-driven transfer and validation workflows
- Onboarding, exits and recurring migrations
TRANSIENT BY DESIGN
Your approval. Your data. Your move.
A company name or user account is not enough. Data access and transfer require independent review, digital company confirmation and separate approvals.
Source
Temporary processingDestination
Temporary processingDestinationAutomatic deletion · 24 hours
Illustration. Select the actual retention period in your case. Evidence, account data and provider backups have separate rules.
Protected connections
HTTPS in transit. API credentials receive additional AES-256-GCM encryption before storage.
Verified authority
Organization- and case-scoped permissions, independent reviewers and a second factor for sensitive approvals.
Limited retention
Temporary migration files: immediately, 24 hours, 7 days or 30 days after completion. Evidence records are treated separately.
Frankfurt data region
The database and private file storage use Supabase in Frankfurt. Server-side application processing uses Vercel’s Frankfurt region.
EU data regions alone do not establish GDPR compliance. Contracts, lawful bases and operational measures also matter. Switona does not claim its own ISO or SOC certification.
CLEAR PRICING. CLEAR RESPONSIBILITY.
Pricing that fits how you use Switona.
One company switch or recurring customer migrations: the commercial model follows your use and the party covering the cost.
For companies
One switch. One price.
One-time price
- No subscription. No recurring fee.
- Quoted after scope and requirements are known
- A provider can sponsor your migration
FOR SOFTWARE PROVIDERS
For software providers
Recurring customer switches.
Usage-based
- Reusable Source and Destination Profiles
- Actual usage at your agreed tariff
- Customer exits and onboarding
For high volume
Repeatable switches at scale.
Enterprise agreements
- Negotiated usage agreements
- Recurring migration volume
- Technical requirements reviewed together
The billing party and commercial approval are confirmed before paid execution.
No invented list prices: scope, complexity and requirements determine the actual quote.
YOUR NEXT CHAPTER
Cloud, database or application. Your next move starts here.
Switch cloud infrastructure
Inventory and assess exportable data and portable artifacts for an IaaS provider change. Plan target resources and operational handover separately.
Move between platforms
Assess data, configurations and dependencies when changing PaaS or managed services. Evaluate proprietary runtimes separately.
Migrate databases
Prepare tables, schemas and relationships across self-managed databases and Database as a Service.
Transfer storage
Move files, objects and metadata between compatible storage services. Validate scope and integrity using manifests and checksums.
Switch applications
ERP, CRM, SaaS and custom business applications: transform business data and preserve relationships.
Return to your own infrastructure
Prepare cloud data for import into your own data center or private cloud and assess target requirements.
Hybrid and edge environments
Transfer defined datasets between cloud, edge and local systems after evaluating connections and formats.
Consolidate systems
Bring data together after acquisitions or modernization across multiple applications, databases and storage locations.
Provider onboarding and exits
For cloud and software providers: create reusable transfer paths for customers joining or leaving a service.
GOOD QUESTIONS. CLEAR ANSWERS.
Before you make your move.
Who can start a switch?+
The switching company, current provider, new provider or migration partner. Every actor uses the same Switching Case.
Do all parties need to already use Switona?+
No. One party creates the case. The independently verified company contact receives the authorization request even without an existing account. A verified sign-in and second factor are required for the digital decision.
What happens after registration?+
Verify your email and set up your company. Then create a case or prepare system connections. An account alone grants no data access. Each case guides you through the required approvals step by step.
Who pays?+
The company, source provider, destination provider or another party can cover the migration. Initiator and payer are independent.
What does Switona cost for companies?+
A direct company receives a one-time migration price after scope and complexity are known. No subscription and no recurring fee.
What does Switona cost for software providers?+
Providers processing recurring customer migrations use usage-based pricing or enterprise arrangements.
Can my new software provider pay for my migration?+
Yes. Both destination and source providers can sponsor migrations. Billing responsibility is explicitly accepted.
What if my software is not supported?+
CSV/TSV, XLSX, JSON, JSONL/NDJSON, flat XML and ZIP packages containing supported files can be read. Configurable REST APIs are also available. Unknown, encrypted or oversized files need a separate review and are never silently accepted.
Does Switona keep our data?+
Temporary migration data is deleted according to the chosen policy: immediately, after 24 hours, 7 days or 30 days after completion. Appropriate reports and metadata are retained separately.
Does AI perform our migration?+
No. AI may assist with interpretation and suggestions in the future. V1 uses deterministic semantic rules. Approved, stored rules execute the processing.
Is Switona only for SaaS?+
No. Data from databases, storage, cloud and on-premises systems can be prepared through suitable exports and profiles. V1 does not automatically move runtimes or whole infrastructures.
Does Switona guarantee EU Data Act compliance?+
No. The Data Act is market context. Switona provides technical switching infrastructure, not legal advice or guaranteed compliance.
Your next environment shouldn’t be decided by your old data.
Choose where you go next. We'll help your data get there.