Skip to content
Data Ocean

Migration - Data Ocean to File Service

To migrate content from Data Ocean to File Service, contact the File Service team at tc-file-service-ug@trimble.com

On request, the File Service team will trigger a migration process to move file metadata from Data Ocean to File Service. Once the migration is complete, files will only be accessible through File Service APIs.

Overview

Responsibilities

  • Integrated applications must update their code to use the new File Service APIs.
  • The File Service team will migrate Data Ocean content to File Service.

Important details

  • This migration moves file metadata from Data Ocean to File Service. The physical files remain in their current location and are not changed.
  • Existing resource IDs and metadata are retained during migration. See the migration guide for information on metadata mapping and changes.
  • Only files with an “AVAILABLE” status are migrated.
  • Once migration is complete, content is only available in File Service and can no longer be accessed through Data Ocean.

Migration process

Migration will look different for every integrator. In most cases, the actual migration should be straightforward once your application code is updated to use the new File Service APIs.

For the simplest Data Ocean use cases, migration proceeds as follows:

  1. Determine which data should be migrated (all data owned by your application or just a subset).
  2. Select a region for content migration and create a Space in that region.
  3. The File Service team migrates all content owned by your application to the newly created Space.
  4. Your application starts using File Service APIs to access stored content.

Note: At this point, your data is no longer accessible through Data Ocean.

Testing

Once the metadata is migrated from Data Ocean to File Service by the File Service team, the application or product using Data Ocean can switch to File Service APIs in a lower environment and test to ensure everything is working as intended. The File Service team will work with you to address any concerns. Once tested, the switch in the production environment can happen.

Example: Simple Data Ocean use case

  • You use Data Ocean for simple upload and download only.
  • You are currently using Data Ocean in the application context and want to use File Service the same way.
  • All of your data is owned by a single application and used in a single product. It is not shared with product lines outside of your control.
  • All of your data is stored in a single geographic region. Or, if your data is stored in multiple regions, you are OK with it being migrated to a single region.
  • All metadata can be migrated as-is; no changes are needed.