Start with the file you have
Move a design system
with a clear plan.
Inspect references, map old assets to new ones, then review exactly which supported properties will change. Keep a readable record of the result.
What should we inspect?
Up to 25,000 layers, 3,000 assets and 5,000 operations per run. Incomplete inspections cannot be applied. Main component contents and locked layers are excluded from layer changes.
New to migration? The sample adds a separate page with Legacy/ and Client/ assets so you can inspect a complete example.
Choose the destination
Map source assets to targets.
On the left: what your file uses now. On the right: what should replace it.
Can’t find a replacement?
Search target names to narrow the first 100 choices. To use assets from another file, open Recipes & targets for the library workflow. Target packs contain keys, not copies of unpublished assets.
| Currently using | Uses | Replace with | Clear mapping |
|---|
Review before applying
Check the changes.
Uncheck anything you want to keep. Anything marked “skipped” will stay unchanged.
Scope and safety notes
Know what happened
Migration report.
Verified properties, skipped operations and remaining mapped references.
Restore is available in this plugin session until the document changes again. A recovery record is a reference file, not a full-file backup or an importable restore script.
| Layer / asset | Change | Target | Result |
|---|