Phase 1: Discovery and Scoping
We begin by understanding the source environment, the data, your goals, and the operational realities. This phase is designed to establish clear scope, priorities, stakeholders, and success criteria before migration begins.
This includes:
• Source platform assessment
• Matter and workspace inventory
• Data volume and complexity
• Identification of priority matters, deadlines, and migration sequencing
• Review of workflows, review work product, and customizations
• Assessment of integrations, automation, and downstream dependencies
• Stakeholder identification and responsibility mapping
• Migration path recommendation
• Definition of success criteria, risks, and open issues
Phase 2: Export Review and Normalization
Once data is exported from the source platform, we review and normalize the package for RelativityOne. This phase focuses on ensuring the exported data is complete, usable, and aligned to the target environment before loading begins.
This may include:
• Load file review
• Path cleanup
• Delimiter, format and encoding checks
• Metadata normalization
• Validation of natives, images, and text
• Family relationship review
• Review of deduplication and processing implications
• Work product mapping decisions
• Identification of missing, inconsistent, or unsupported data elements
• Preparation for RelativityOne field mapping and workspace configuration
Phase 3: Pilot Migration
Before a full move, we recommend a test or pilot load whenever possible. This gives the client and project team an opportunity to validate the migration approach, confirm expected outcomes, and identify any adjustments before broader rollout.
This helps validate:
• Counts
• Field mapping
• Searchability
• Image and text behavior
• User workflows
• Security and access expectations
• Work product carry-forward results
• QC methodology and validation standards
• Readiness for production migration
• Gain your trust
Phase 4: Full Throttle Migration
After the pilot is approved, the full migration proceeds in a controlled sequence. Depending on the engagement, that may mean one matter, multiple matters, or a wave-based rollout. This phase is focused on executing the agreed-upon migration plan while minimizing disruption and maintaining visibility into progress, issues, and dependencies.
This may include:
• Migration by workspace, matter or priority wave
• Controlled scheduling and cutover coordination
• Ongoing monitoring of counts, exceptions, and transfer status
• Issue tracking and resolution during migration
• Coordination with client stakeholders on timing and business impact
• Execution of the approved migration sequence and timeline
Phase 5: Validation and Cutover
We finalize reconciliation, support user testing, and help manage the transition to the new environment so the team can move forward confidently. This phase confirms that the migrated data meets agreed expectations and that the client is prepared for go-live in RelativityOne.
This may include:
• Final reconciliation of counts and data populations
• Validation of metadata, families, text, images, and work product
• User acceptance testing support
• Signoff against predefined success criteria
• Final review of risks, issues, and post-migration action items
• Cutover support and transition planning
• Post-migration stabilization and follow-up recommendations