Optimizer Hints Ignored by default in ADW, where honored by default in ATP When migrating data to Autonomous Database, table statistics are gathered automatically during direct path load operations. If direct path load operations are not used, such as with SQL Developer loads, the user can gather statistics manually as needed. When migrating an existing database that uses optimizer in parallel hints, ADB will ignore those by default. Because ADB runs in a highly tuned exadata environment, most database operations should run faster or at least as well as database tune with lots of hints to perform faster. Should hints be required for some reason, they can be explicitly re-enabled.
Autonomous Data Warehouse ignores optimizer hints and PARALLEL hints in SQL statements by default

Use REST verb POST to create Autonomous Database with REST AP
https://docs.cloud.oracle.com/iaas/api/#/en/database/20160918/AutonomousDatabase/CreateAutonomousDatabase

The main migration tool for migrating to ADB is Data Pump. You can export your schemas and import them into ADB using Data Pump. To sync up the additional/incremental changes on the source database during the export/import process you can use GoldenGate or GoldenGate Cloud Service to replicate those changes to ADB.
In the current release you cannot use physical migration methods like backup/restore. Data Guard, database clones, and transportable tablespaces to move your existing database to ADB.
https://www.oracle.com/database/technologies/datawarehouse-bigdata/adb-faqs.html#MIGRATION