SWITONA FOR CLOUD & SOFTWARE PROVIDERS

An easier way in. A clearer way forward.

Reusable technical transfer paths for onboarding, provider changes and exits across cloud, platform, storage and software services.

Start a switch Talk to Switona

INFRASTRUCTURE, NOT ANOTHER PROJECT

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.

Inventory source and scope

Evaluate export and import paths

Approve the transfer

Document results and handover

Your services. One neutral migration layer.

A company account can be created independently of a switch. Configure and test your system’s REST API once under Connections. Source, destination and authorizations are checked for each case. This example shows part of a source configuration; credentials are entered separately.

Talk about Switona for providers

EXAMPLE REST SOURCE CONFIGURATION
{
  "baseUrl": "https://api.example.com",
  "auth": { "method": "bearer" },
  "testPath": "/health",
  "entities": [{
    "table": "customers",
    "entity": "customer",
    "readPath": "/customers"
  }]
}

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