1. Administering Oracle Content Management
  2. Migrate Oracle Content Management
  3. Migrate Files to Oracle Content Management Assets
  4. Submit a File Migration Service Request

Submit a File Migration Service Request

When your Oracle Content Management instance and target repositories are set up, and you’re ready for your migration, you must submit a migration request. We recommend that you give two weeks advanced notice. Oracle will attempt to schedule your migration based on your requested date. If a migration needs to follow a very specific schedule, submit a service request specifically to facilitate scheduling in advance.

Note:

You don't need to submit a service request if you're migrating fewer than 500,000 files from Oracle WebCenter Content (you can use Archiver and Content Capture to migrate a moderate number of files from Oracle WebCenter Content).

To submit your migration service request:

  1. Sign in to Oracle Cloud Support.
  2. Create a new service request.
  3. For the Product, select Oracle Content Management.
  4. For the Problem Type, select Service Instance Migration.
  5. Attach the CSV file to your request.
  6. Submit your service request. Then make sure to keep up with any service request updates so you can provide additional information when necessary.
  7. Oracle Support will work with you to gather additional required details about your migration, including your source and target information, field mappings, and taxonomy definitions.
  8. After the details are gathered, Oracle Support will coordinate with the migration team to finalize a migration date that works for you and Oracle. The service request will be updated with the date and time your migration will start.
  9. After you confirm in the service request that you approve the migration start date and time, Oracle Support and the migration team will execute your migration request.

    Updates will be made to the service request to show how the migration is progressing. The data migration will be done at the back end; no action is required at your end other than to keep up with any service request updates, and to validate the migration after it's done.