PLANNING A TREE ASSET REGISTER MIGRATION

Move a register through a documented mapping and pilot rather than a single unreviewed transfer. Preserve identity, evidence relationships and an archive of the original before considering the receiving record authoritative.

Project/site:
Prepared by/date:
Version:

Source inventory
Identify the dataset, version and evidence set.
Notes:

Destination requirements
List the supported fields and formats.
Notes:

ID translation
Document any approved identifier relationship.
Notes:

Pilot scope
Choose representative test records.
Notes:

Acceptance record
State checks, exceptions and the responsible reviewer.
Notes:

CHECKS
[ ] Keep the original dataset and its issued outputs retrievable.
[ ] Resolve unsupported fields before the full transfer.
[ ] Compare totals, sample IDs, units and evidence references after migration.

Outstanding questions:
Source references:
Review and next action:

Scope: No particular application’s import coverage is guaranteed; use its current supported workflow and test results.

This is a general worksheet, not an automated application feature.
https://canopyapp.app/resources/tree-asset-register-migration