1. Administering Oracle Content Management
  2. Migrate Oracle Content Management
  3. Migrate Files to Oracle Content Management Assets
  4. Migration Process

Migration Process

Migrations follow these basic steps:

  1. If a migration needs to follow a very specific schedule, submit a service request specifically to facilitate scheduling in advance. Otherwise you'll submit your service request in a later step. We recommend that you give two weeks advanced notice.

    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).
  2. Map your source data structure and security to Oracle Content Management asset features.
  3. Create an Oracle Content Management instance.

    Note:

    This step isn't necessary if you already have an Oracle Content Management instance, for example, if you're migrating files from a Documents folder.

    For large deployments you may want to:

    • Set up the appropriate primary and non-primary environments for Oracle Content Management (for example, development, staging, and production) within the Oracle Cloud Infrastructure compartment.
    • Enable Identity and Access Management (IAM) to support SSO and user/group synchronization between Active Directory and IAM for the staging identity stripe.
  4. Create the Oracle Content Management structure based on your planning. The repositories you create will be the targets your data will be migrated to. The target repositories and all associated taxonomies must remain empty until migration has been completed.

  5. Migrate your files and metadata to Oracle Content Management.

    A “migration” targets a single asset type in a single repository. Thus, it's likely that you'll require multiple “migrations” to complete the transfer of your data. For example, the Accounts Payable department of a company may have multiple document types that will be represented by multiple new asset types: Invoice, Purchase Order, Shipping, and such. Each of these is a separate migration.

    The migration can be divided into multiple migration passes.

    1. The primary pass is expected to migrate the bulk of the content and thus be the largest pass. While this migration proceeds the source system is assumed to still be in production.
    2. After the primary migration is complete, a “delta” migration can be performed which migrates only the changes that have occurred since the data export for the primary migration was produced.
    3. Multiple deltas are supported until a final delta is small enough to be completed in an acceptable downtime window.
    4. Prior to the final delta, the source system is shutdown for the last time. The delta migration is performed, after which you'll transition production to the new asset-based implementation.

    Depending on the source and volume of files you're migrating, you'll perform different steps.

    Source Repository Migration Scenarios
    Oracle WebCenter Content

    For high-volume migrations (more than 500,000 files):

    For moderate-volume migrations (fewer than 500,000 files):
    External repository

    For high-volume migrations (more than 500,000 files):

    For moderate-volume migrations (fewer than 500,000 files):

    • Use Content Capture to import content and metadata from external repositories into Oracle Content Management.
    Oracle Content Management Documents

    For migrations of any volume:
  6. Continue with the next migration (the next target repository and asset type) until all your files and metadata have been migrated.
  7. Communicate the change to your users.

File Migration FAQ