Canva Integration Migration Program

Overview

Separate provider-contract, credential, application-data, and user-experience migrations. Preserve reversibility and reconcile every asynchronous or mutating operation before moving the next cohort.

Prerequisites

• Source and target operation/capability matrix
• Data inventory, rights, retention, consent, and identifier map
• Cohort plan, feature flag, validation sample, rollback, and owner

Instructions

Step 1: Define parity honestly

Use Read and Grep to map supported, changed, preview, unavailable, and intentionally retired operations. Do not invent workarounds for unsupported provider behavior.

Step 2: Design identity and consent