Console
Documentation/Migration and compatibility

Migration and compatibility

Move an integration without importing unsafe assumptions.

From direct Cloud API access

Create a Sqkii organization and connect the customer-owned assets through Embedded Signup. Replace direct Graph requests with documented Sqkii resources, move credentials into scoped keys, and register your event receiver. Preserve idempotency keys and customer consent records.

Do not copy a permanent Meta token into a browser application. Sqkii's backend obtains customer-scoped access through the approved onboarding flow.

From another provider

Confirm number and coexistence eligibility before disconnecting an existing provider. Export data you are entitled to retain, respect your retention policy and test ownership changes with Meta's documented flow. Do not promise a zero-downtime migration without a verified account-specific procedure.

From WACRM

Sqkii selectively reuses MIT-licensed components; it is not a database-compatible WACRM upgrade. WACRM account configuration does not map one-to-one onto Sqkii organizations with multiple projects and numbers. Plan a reviewed import rather than pointing Sqkii at an existing WACRM database.

API upgrades

Pin client versions, test against the simulator and compare OpenAPI contracts. Treat Meta Graph API, Embedded Signup and Sqkii API versions as separate compatibility surfaces.

Prepared 18 November 2026 · Sqkii Pte. Ltd.