The image has 5 parts, which illustrate the 5 steps in the migration process.

The first part is labeled with a numeral 1 and a label “Prepare Cloud and Instantiate Cloud Standby (2 Cloud OHs: Source and Target DB Versions)”. Next to the label is shown an on-premises source database labeled 11.2 pointing to a DBCS target database labeled 11.2, and the label on the arrow reads “Instantiate Standby”.

The second part is labeled with a numeral 2 and a label “Enable TDE and Encrypt Standby (optional)”. Next to the label is shown an on-premises source database labeled 11.2 pointing to a DBCS target database with a lock on it labeled 12.2, and the label on the arrow reads “Real-time Encrypted Redo”.

The third part is labeled with a numeral 3 and a label “Data Guard Switchover and Upgrade Cloud (Downtime Starts: On Premise Read-Only Queries Allowed, Upgrade Cloud Primary)”. Next to the label is shown an on-premises source database and a DBCS target database with one arrow pointing from On-premises to Cloud and another arrow pointing from Cloud to On-premises, and the label on the arrows reads “SWITCHOVER and Upgrade”. The target cloud database is labeled 11.2, and it points to another cloud database labeled 12.2, indicating the upgrade.

The fourth part is labeled with a numeral 4 and a label “Plug into CDB”. Next to the label is shown an on-premises source database labeled 11.2 pointing to a DBCS target database labeled 12.2, and the label on the arrow reads “CDB Plugin Switch App to Cloud”. Next to the target cloud database is a CDB containing 3 PDBs and labeled 12.2 CDB, indicating the plug-in.

The fifth part is labeled with a numeral 5 and a label “Fallback if required Activate 11g Database (Data Loss)”. Next to the label is shown an on-premises source database labeled 11.2 and the DBCS target CDB with no arrows between them, and the label between the databases reads “Just Discard Cloud Database”.