☑️ Scope the matters and data
Identify which matters, workspaces, custodians, and data sets are included in the migration, along with any items that should be excluded or handled separately.
☑️ Prioritize what moves first
Determine which matters are most urgent based on activity level, deadlines, client needs, or business importance, and decide whether the migration will occur all at once or in phases.
☑️ Identify the source platform and export method
Confirm the current platform or platforms involved and understand what export options are available, including whether data will come from live environments, archives, backups, or flat-file exports.
☑️ Inventory data, metadata, and work product
Document what needs to carry forward, including natives, images, text, metadata, coding decisions, issue tags, redactions, productions, and other review-related work product.
☑️ Review workflows, customizations, and integrations
Assess any custom applications, scripts, field structures, layouts, third-party integrations, or automated processes that may need to be recreated, replaced, or retired in RelativityOne.
☑️ Confirm processing, deduplication, and search expectations
Understand how data was originally processed, what deduplication methodology was used, and whether current search, analytics, or review behavior needs to be preserved in the new environment.
☑️ Review security, compliance, and legal requirements
Identify any user access restrictions, ethical walls, client-specific security expectations, retention obligations, legal hold considerations, or regulatory requirements that could affect migration planning.
☑️ Define the migration approach and timeline
Establish whether the migration will be handled by workspace, matter, or wave, and align on target start dates, milestones, dependencies, and expected completion timing.
☑️ Assign stakeholders and responsibilities
Identify the key contacts on both sides of the project and clarify who is responsible for technical coordination, project management, testing, approvals, and final decision-making.
☑️ Establish QC, validation, and signoff criteria
Define how success will be measured, including count validation, metadata accuracy, family integrity, work product carryover, user testing, and final acceptance procedures.
☑️ Document risks and open issues
Capture known concerns, dependencies, data gaps, technical limitations, and unanswered questions early so they can be addressed before they impact the migration.