migration-analysis

To analyze Sui package upgrade readiness, assess token transitions, object-layout changes, and UpgradeCap policy compliance between V1 and V2. This identifies compatibility concerns and verifies whether type identities are preserved or altered during the migration.

Stranded assets in Sui migrations are tokens or objects left inaccessible after an upgrade. You can identify them by tracing token flow paths and pre-upgrade inventory using Move type information and object ownership data to model recovery options.

UpgradeCap lineage determines the upgrade policy enforced on a Sui package. Analyzing it verifies whether upgrades preserve or alter type identities and ensures the planned migration path complies with the authorized upgrade rules.

Yes, you can detect deprecated functions when upgrading Sui Move packages by modeling safe upgrade paths across V1 and V2. This analysis quantifies risks by mapping object-layout changes and highlighting deprecated logic.

The best way to audit a Sui package migration is to leverage Move type information and object ownership data to quantify risk exposure. This approach outlines compatibility concerns, stranded assets, and remediation guidance for auditors.

Sui package upgrades leave objects stranded when object-layout changes break previous ownership data or type identities. You can model recovery options by tracing pre-upgrade inventory and token flow paths against the new V2 package layout.