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/importsGeneric import endpoint.
POST/imports/vapiCompatibility import route for source-platform-shaped payloads.
POST/import/vapiLegacy-compatible alias for the import route.

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 references

These external docs are useful when mapping customer imports and migration expectations. They are not Aywa documentation and do not imply affiliation.

Vapi API reference Vapi tools overview Vapi default tools Vapi assistant-request server flow Vapi webhook testing flow