RelativityOne Migration FAQ

Migration to RelativityOne refers to the process of moving your eDiscovery data, users, workflows, and customizations from on-premises or other legacy platforms to the RelativityOne cloud environment. This transition helps organizations leverage the security, scalability, and advanced features of Relativity’s SaaS platform.

Migrating to RelativityOne allows your organization to:

• Access the latest product features and security enhancements automatically.
• Reduce IT maintenance overhead.
• Scale resources as caseloads fluctuate.
• Enable secure remote access and streamlined collaboration.

Begin by assessing your current environment: evaluate case data, user roles, custom apps, and compliance requirements. Set migration goals; define a project timeline; and involve stakeholders from legal, IT, compliance, and business operations.

Prioritize current and active cases, critical legacy projects, and ongoing workflows. Archive or leave behind closed, inactive, or nonessential matters to reduce cost, complexity, and risk during migration.

Successful migrations require a cross-functional team, typically including:

• IT and security staff
• Legal operations and case managers
• End users (reviewers, admins)
• Project managers
• Compliance/risk officers

Working together ensures all perspectives and requirements are addressed.

Engaging a Relativity-certified migration partner is highly recommended. Specialists like ProSearch bring expertise, proven tools, and process automation that lower risk, accelerate timelines, and ensure defensibility.

Best practices include running pilot migrations with noncritical data, cleaning and validating data before transfer, documenting every step, and maintaining detailed chain of custody records. Involving experts and strictly managing permissions further reduce risk.

Use secure, encrypted transfer protocols, and leverage RelativityOne’s built-in compliance and audit features. Validate that all data, metadata, and permissions have transferred properly before go-live. Maintain thorough documentation for legal defensibility.

A pilot migration involves moving a small, noncritical dataset or project first. This lets you test your approach in a low-risk environment, identify issues, and adjust your process before completing the full migration.

Provide tailored, role-specific training to all users and stakeholders before the platform goes live. Focus on RelativityOne’s new features, process changes, and best practices. Ongoing support and communication are key for user adoption.

Audit all custom workflows, scripts, and integrations early in the process. Some may need updating or replacement to be compatible with RelativityOne. Involve technical experts to map requirements and test customizations premigration.

A post-migration “hypercare” phase is essential. Monitor system performance; resolve issues rapidly; and collect user feedback. Regularly review your workflows, and adopt new RelativityOne capabilities to maximize value.

Track completion rates, user satisfaction, data accuracy, system performance, and case productivity. A successful migration preserves data integrity, minimizes business disruption, and delivers improved capability and efficiency.

Read this two-part article series that addresses these and other questions about RelativityOne migrations in more detail:

• Part 1 – Cloud Migration for E-Discovery and RelativityOne
• Part 2 – Making the Leap: Practical Guidance for Migrating to RelativityOne

Or contact us to talk with a ProSearch specialist for a deeper dive into planning, process, and optimization strategies.