Switching company
Tell us where your data is and where it needs to go.
Choose your roleFOR SOURCE PROVIDERS
Provide the source. We handle the handover.
Standardize customer exits with Source Profiles, a defined scope and a documented handover. Your team does not have to configure the destination.
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 roleFROM 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.
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
customerIdstringorganizationNamestringemailAddressstringCLEAR 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.
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.