Aywa RuntimeDocumentation
Website Create account

Migration

Switch execution, keep the assistant contract familiar.

The migration workflow is for compatible assistant configurations from third-party voice platforms. The goal is to move execution into private infrastructure while keeping provider mapping, tools, and validation steps explicit.

Positioning boundary

Aywa Runtime is independently developed. Third-party product names are used only to identify supported import sources, compatibility fields, or customer migration context.

Independent runtime: compatibility imports help teams migrate assistant configurations they already own. Aywa Runtime is independently developed and is not affiliated with, endorsed by, or sponsored by third-party voice platforms.

Migration flow

Export

Export assistant, phone number, tool, server, and credential references from the current platform.

Import

Use the runtime importer to preserve compatible fields and map source ids to runtime ids.

Map

Attach provider credentials, webhook credentials, BYO SIP trunks, and storage settings in the private runtime.

Validate

Run staging calls, compare tool calls, inspect timelines, then cut traffic gradually.

Importer endpoints

The runtime exposes import routes for compatibility workflows. Source ids can be mapped to runtime ids for later lookup and phased cutovers.

POST/importsImport compatible assistant configurations with a neutral sourceFormat or compatibilityProfile.
Import request 
{
  "sourceFormat": "compatible_assistant_export",
  "compatibilityProfile": "generic_assistant_v1",
  "sourcePlatform": "vapi",
  "apiKey": "source_private_key",
  "dryRun": true,
  "mode": "upsert",
  "resourceTypes": ["assistants", "tools", "phoneNumbers", "credentials"]
}

ID mapping and customer SQL patches

The migration assistant is available inside the private runtime dashboard under Migration. It imports compatible resources, builds a source-id to runtime-id mapping table, and can generate a reviewable SQL pack for the customer-owned tables that still store source ids.

Safe by design: Aywa Runtime generates SQL, row-count previews, and an explicit transaction. It does not connect to or mutate the customer's application database automatically. Review the file in staging, back up production, then apply it through your normal database release process.

Mapping table

Creates or updates aywa_import_id_mappings with organization, source provider, resource type, source id, runtime id, action, and source name.

Reference inputs

For each customer table, provide table name, column name, resource type, optional filter column, optional filter value, and text or uuid casting.

Patch output

Generates SELECT count(*) previews plus UPDATE ... FROM statements that replace source ids with runtime ids through the mapping table.

Runtime dashboard request shape 
{
  "organizationId": "org_...",
  "sourcePlatform": "vapi",
  "mode": "upsert",
  "sqlMappingTable": "public.aywa_import_id_mappings",
  "sqlReferenceUpdates": [
    {
      "tableName": "public.calls",
      "columnName": "assistant_id",
      "resourceType": "assistants",
      "filterColumn": "workspace_id",
      "filterValue": "customer_workspace_123",
      "valueCast": "text"
    },
    {
      "tableName": "public.tool_runs",
      "columnName": "tool_id",
      "resourceType": "tools",
      "valueCast": "uuid"
    }
  ]
}

The copied fullMigration SQL contains the mapping-table schema, mapping upserts, reference previews, reference updates, and BEGIN/COMMIT boundaries. Third-party names in this workflow identify the migration source only; the resulting resources run on Aywa Runtime.

Validation checklist

Assistant

System prompt, first message, model settings, voice settings, transcriber settings, metadata.

Tools

Function names, parameters, timeouts, server URL, credentials, headers, and response handling.

Webhooks

Assistant, phone number, tool, and account fallback server targets.

Telephony

BYO SIP trunk, phone number binding, inbound route, outbound caller id, DTMF, transfer behavior.

Artifacts

Transcript, recording, structured output, end-of-call report, and cost breakdown.

Latency

Endpointing, first model token, first TTS audio, barge-in timing, and tool roundtrip.

Compatibility boundary

Aywa Runtime can import compatible assistant configurations from existing customer-owned exports. The import profile identifies the format being mapped; it does not imply affiliation, endorsement, or shared ownership with any third-party platform.

Mapped

Assistant instructions, model settings, voice settings, tools, webhook targets, phone number bindings, and source id references.

Re-attached

Provider credentials, SIP trunks, storage destinations, billing ownership, and production deployment settings.

Validated

Turn handling, tool calls, endpointing, barge-in behavior, webhook retries, and call artifacts before traffic cutover.