Migrate Files to Oracle Content Management Assets

If you currently manage your files in Oracle WebCenter Content or an external repository, there are many reasons to migrate to Oracle Content Management assets. This topic answers some of the questions you may have about migrating to help you decide how to proceed. For additional answers, refer to File Migration FAQ.

Why should I migrate my content to Oracle Content Management assets?

Moving your content to Oracle Cloud andOracle Content Management provides the following benefits:

• Bring your own license (BYOL), simplifying cloud purchasing and consumption
• Autoscale your environment based on resource usage and user traffic
• Automated zero-downtime patching and upgrading
• Continuous monitoring
• Create a private Oracle Content Management instance accessible only through FastConnect
• Built-in high availability and disaster recovery
• Always encrypted content

Converting your files to Oracle Content Management assets provides additional benefits:

• Secure REST APIs for content management and delivery
• Full-text multilingual search
• Role-based search results
• Smart tagging powered by artificial intelligence (AI)
• Video lifecycle management from creation to streaming with CDN
• Site, portal, and microsite creation capabilities
• State-of-the-art digital asset management (DAM)
• Headless experiences
• Marketing collaboration
• Secure document management with granular permissions

What are my migration options?

Depending on the source and volume of files you're migrating, you use different methods to migrate your content.

Source Repository	Migration Method
Oracle WebCenter Content	For high-volume migrations (more than 500,000 files): Oracle WebCenter Content 12c—Use the Object Storage Migration Tool to export your source files to OCI object storage, export your source file metadata to CSV, then work with Oracle Support to finish the migration. Oracle WebCenter Content 11g—Oracle recommends using the following approach to migrate files from Oracle WebCenter Content 11g to Oracle Content Management assets. Upgrade your on-premise Oracle WebCenter Content 11g instance to 12c, and then follow the method above. For moderate-volume migrations (fewer than 500,000 files): Use Archiver to export your files to HDA format, and then use Content Capture to import the content and metadata into Oracle Content Management.
External repository	For high-volume migrations (more than 500,000 files): Export your files to a common file system, upload them to Oracle Cloud Infrastructure object storage using the Object Storage command line tool or offline data transfer, export your source file metadata to CSV, then work with Oracle Support to finish the migration. 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: Work with Oracle Support to perform the migration directly from Documents to assets.

What are the prerequisites for migration?

• Define the target environment and provide the mapping from the source data to the target Oracle Content Management environment.
• Redefine your solution leveraging the features of Oracle Content Management, such as repositories, asset types, taxonomies, and such. This includes configuring the asset type to accept all of the file types (based on file extension) that will be migrated.
• Reimplement security using the Oracle Content Management features of groups, roles, repository security, and granular taxonomy security.
• Define the mapping between source (Oracle WebCenter Content, external repository, or Oracle Content Management Documents) and target (Oracle Content Management).