timeback-migrate

To migrate Timeback calls to the SDK without behavior changes, run a Phase 1 audit to inventory direct OAuth, OneRoster, and Caliper requests. The process then proposes SDK equivalents, migrates approved calls in dependency order, and verifies that no raw calls remain before cleanup.

Yes, you can incrementally swap custom OAuth token handling for the Timeback SDK. The migration proposes SDK equivalents, migrates approved calls in dependency order, and removes redundant token management only after developer confirmation at gated checkpoints.

The best way to audit existing OneRoster and Caliper integrations is running a Phase 1 audit. This scans the codebase for manual requests, OAuth token management, and Edubridge or PowerPath calls, recording their locations and contexts into a migration manifest for developer confirmation.

Yes, the Timeback SDK migration supports Edubridge, QTI, and PowerPath calls. The audit scans the codebase for these specific direct calls, proposes official SDK equivalents, and migrates them incrementally while preserving existing product behavior.

Yes, you need Timeback API credentials or course IDs to migrate to the SDK. Config setup references existing Timeback courses and maps environment variables to generate a timeback.config.json, requiring codebase access and developer confirmation at gated checkpoints to proceed.

Ambiguous Caliper or OneRoster calls are documented for manual review during verification. The migration enforces decision gates requiring developer approval before proceeding, ensuring excluded or ambiguous cases are explicitly recorded rather than automatically converted.