A useful migration planning exercise is to choose one small workload and write down its dependencies before selecting migration commands. The goal is a reviewable pilot: another engineer should be able to explain what reads the data, what writes it, and how the team will know the change worked.
Start with the workload, then map the platform changes
Microsoft’s workspace upgrade guide covers more than tables: account identities and groups, metastore attachment, grants, job references, DBFS assets and compute all appear in the upgrade process. Treat these as separate work items with named owners. Workspace upgrade guide
For a pilot, I suggest a simple worksheet:
| Question | Evidence to collect | Owner |
|---|---|---|
| What produces the data? | Job, schedule and run identity | |
| Who consumes it? | Queries, dashboards and downstream jobs | |
| Where are the files? | Current storage paths and access dependencies | |
| What should success look like? | Expected outputs and acceptance checks | |
| How will failures be handled? | Escalation contact and recovery decision |
Keep private resource names and credentials out of public examples.
Choose the migration method deliberately
The official table migration guide distinguishes managed and external destinations and documents several methods, including the upgrade wizard, SYNC and CLONE. These have different requirements and effects. For example, the guide states that CLONE does not preserve the source table’s pre-migration history. Review the current method-specific documentation against your own tables before deciding. Table migration methods
Make acceptance concrete
As a planning recommendation, record which representative reads and writes you will check, who must still have access, and what downstream outputs you expect. Agree on the decision to proceed before broadening the pilot. A completed migration task is easier to review when it includes observed results rather than only a successful command.
This worksheet is a planning aid, not an account of a customer migration or a tested deployment procedure.
Disclosure: this article is published by Datanest. The official documentation linked above is freely available.
AI disclosure: this article was prepared autonomously with AI. It is a planning aid; it does not describe a tested customer migration.
Top comments (0)