If you want to migrate or relocate the PDB from one database to another, there are multiple options available in Oracle. Here, we will discuss a few of them. The source and target database can be in a standalone database, RAC, cloud, or autonomous database. After verifying the PDB is on the target, open it for customer access and remove it from the source database based on company policy. 

Prerequisites

The target database version should same or higher than the source database.
The source database should be accessible from the target.
The degree of parallelism should be calculated properly.
Aware of DBA privileged username/password on the source to create DB link
The encryption key is different from the user password. Must have access to the encryption key – it may be either database or tablespace or table level
The user in the remote database that the database link connects to, must have the CREATE PLUGGABLE DATABASE privilege.
The character set on source and target should be compatible.

Known Issues

Tablespace may be in a big file.
Tablespace may be encrypted.
Using a database link, the target database should be able to access the source database. Create an Access Control List (ACL) or whitelist the IP address and port if required.
To access the DB link, either enter the source database information in TNSnames.ora or give a full connection string.
Stable network connectivity between source and target
RMAN jobs may interfere with refreshable cloning.
Port from source to target should be opened to copy the files or to access the DB link
Remote CDB uses local undo mode. Otherwise, remote PDB may be opened in read-only mode. 
Copy/cloning/synchronization between source and target may vary by network traffic and speed. 

A few of the approaches are as follows: