motoko-base-to-core-migration

To migrate a Motoko project from mo:base to mo:core, apply a structured six-phase playbook covering mechanical import renames, data-structure migrations, and persistent actor upgrades. This workflow ensures deterministic upgrade practices and preserves canister state.

Handling Motoko data-structure migrations requires mapping existing structures to new equivalents, such as Buffer to List, HashMap or TrieMap to Map, and TrieSet to Set. The process includes in-place mutations and verification steps to maintain data integrity.

Yes, you can preserve canister state when upgrading Motoko actors to mo:core by following the persistent actor upgrade path. This strategy enforces deterministic upgrade practices and provides build and audit steps to maintain state across upgrades.

The mo:base to mo:core migration workflow supports phase-driven migration across multiple canisters. It defines acceptance criteria for safe deployments and includes a production rollout plan to ensure zero downtime deployments.

To verify a Motoko canister upgrade after migrating imports to mo:core, use the provided verification and upgrade-testing templates. These templates ensure builds succeed, interfaces remain compatible, and acceptance criteria are met before production rollout.

A phase-driven plan for mo:base to mo:core migration is needed to safely manage mechanical import renames, data-structure conversions, and persistent state adjustments. It enforces deterministic upgrade practices and defines audit steps to prevent state loss.