Phase 1 - Discovery and Planning
- Last Updated: October 6, 2026
- 2 minute read
- Progress Data Cloud
- Documentation
Note:
This phase can be performed by the tenant, the Progress Delivery Team, or both. However, someone from Progress should be involved in all aspects of this phase.
Use this phase to understand what you have today, decide where the migration is going, and choose the approach that fits the data and downtime requirements. By the end of this phase, you should know the source environment, the size and shape of the data, the target region, capacity in PDC, the migration option to use, and the runbook to follow.
Start by inventorying the source environment, then assess the data and define the target sizing and migration path before you create the runbook.
- Create an inventory—Document the MarkLogic version, application servers, ports, databases, forests, indexes, security realms, encryption settings, custom code, triggers, scheduled tasks, and whether Content Processing Framework (CPF) or Transparent Data Encryption (TDE) are in use. Gather this information through automated discovery where possible, and manual review where necessary.
- Assess the data—Review how much data you have, how it is organized, what the URI patterns look like, how much binary content it includes, whether it uses triples or rows, and whether replication, high availability, or disaster recovery is required.
- Select the target region and sizing—Review the storage class, input/output operations per second (IOPS), compute profile, encryption at rest, and network connectivity you need for PDC.
- Choose the migration option—Review the Tools and scenarios topic and select the approach that best fits the environment.
- Create the runbook—Document the Responsible, Accountable, Consulted, Informed (RACI) roles, change window, backout plan, contact tree, and validation criteria for the migration.