Make the change reviewable.

Use a reversible, reviewer-approved sample to check mapping and the bank connection before routine operation.

Use identifiers and transaction populations—not matching amounts alone—to establish a duplicate.

A mapping change needs an owner, scope and historical-effect check before it touches the books.

A cost workflow depends on supplied inputs; it does not prove inventory quantities, valuation or completeness.

Define what is already recorded before importing older settlements or changing connectors.

Treat migration as a boundary and acceptance exercise—not simply connecting a second tool.

Package the scope, source records, reconciliations and open questions—not just a folder of exports.

Exports need context, identifiers and known limitations; they are not a complete substitute for access planning.