SupportPreview and apply Piece migrations
Inspect required configuration or schema changes before applying a supported Piece migration to a draft or managed resource.
How this fits into Lead360Explore Ask360 Piece StudioUnderstand the commercial operating model behind versioned Ask360 roles.- 01
How Lead360 helps
- 02
Before you begin
- 03
Complete the workflow
- 04
Understand the key controls
How Lead360 helps
Piece migrations provide an explicit path for moving older or changed configuration into the current supported structure. Preview shows proposed changes and blockers first, while apply records the controlled result instead of rewriting large sections without review.
When to use this workflow
Use migrations when Piece Studio reports an older configuration, resource format, or managed release that requires a supported transition.
Before you begin
Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.
- Identify the source Piece revision and migration target.
- Review current consumers, custom behavior, resources, and version history.
- Create or confirm a recoverable draft path before applying changes.
Complete the workflow
Follow the steps in order and stop when a required resource, permission, review, or approval is missing.
- Open the migration action for the intended Piece.
- Run Preview and inspect every proposed change, warning, and blocker.
- Resolve incompatible resources and preserve required custom behavior.
- Apply the migration to the supported draft target.
- Validate, compare the diff, rerun Arena scenarios, and publish only after approval.
Understand the key controls
Preview first
Preview is read-only and should be the basis for deciding whether and how to migrate.
Draft before publish
A migration result still requires validation, testing, and explicit publication.
Consumer compatibility
Existing consumers remain tied to their current versions until updated through their own workflow.
Release compatibility
Review managed base releases and resource requirements shown by the migration so the destination draft does not depend on unavailable capabilities.
Confirm the result
Do not rely on a success message alone. Confirm the saved state and any live effect in the product area that owns the final record.
- Compare the migrated draft with preview and source behavior.
- Run validation and the established scenario set.
- Confirm no consumer changed automatically.
Troubleshooting
Preview reports a blocker
Resolve the named unsupported capability, resource, field, or custom behavior instead of applying a partial manual rewrite.
Behavior changes after migration
Compare the exact diff, model, memory, and resources, then revise and rerun the same Arena scenarios.
Frequently asked questions
Does applying a migration publish the Piece?
No. The migrated draft must complete normal validation, testing, review, and publication.
Will migration update every consumer?
No. Consumer references remain separate and must be reviewed and updated explicitly.
Continue with Lead360
Use this workflow in Lead360
Put this guide into practice with a 14-day free trial of Lead360 Pro early access, or continue learning through the related collection.