Verifying what someone else built.
WHAT YOU CAN TEST
Whether it meets your requirements Whether it works in your environment Whether it handles your data Whether it performs adequately Whether it integrates correctly
WHAT YOU CANNOT DO
Fix what is wrong.
WHAT THAT CHANGES
Findings become negotiation, not defect reports.
WHAT TO TEST BEFORE ACCEPTING
Every requirement stated in the contract Configuration relevant to you Migration of your existing data Integration points Performance at your volume
WHY DATA MIGRATION SPECIFICALLY
It is where most implementations encounter serious problems.
WHAT TO AGREE IN ADVANCE
Acceptance criteria Who tests what What happens when criteria are not met How defects are classified and resolved
WHAT TO RETAIN
Evidence of what was tested and found.
WHY
It supports the commercial conversation.
WHAT TO TEST AFTER EVERY VENDOR UPDATE
Your critical paths.
WHY
Their changes are not made with you in mind.
WHAT TO NEGOTIATE
Notice before changes, and a test environment.
WHAT TO BUILD
Automated checks of your critical paths against their system.