Migration of business processes, I&T service data and infrastructure is prepared within the enterprise's development methods, with audit trails and a recovery plan in case the migration fails: the migration plan takes in networks, hardware, software and operating systems, master files and transaction data, archives and backups, interfaces to other systems, procedures, system documentation and similar items; the process conversion plan deals with changes to procedures, revised roles and control procedures; the data conversion plan leaves data values unaltered unless a business reason makes a change unavoidable, and any change is documented and approved by the data owner; backup and archived data are retained as business and regulatory needs require; the conversion is rehearsed and tested before it is done for real; the timing and completeness of cutover are coordinated and checked so that the move is smooth and no transaction data is lost, falling back to manual processing where needed; every system and all data are backed up just before conversion, with audit trails that allow it to be traced back and a recovery plan for rollback and fallback; the plan sets out how data will be collected, converted and checked, how conversion errors will be found and resolved, and how original and converted data will be compared to confirm integrity; and, where the risk justifies it, conversion risk, continuity planning and fallback are taken into account.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.