Relativity to iManage Data Migration
Moving documents from Relativity to iManage? Settle automates the mapping between Relativity's eDiscovery workspace model and iManage's document management architecture — preserving document metadata, coding decisions, and folder structures.
Working with enterprise teams on active migration programs
Days
to production-ready mappings
Roughly half
the cost of consulting-led delivery
Every row
validated before go-live
Enterprise migrations routinely run months behind schedule. Yours doesn't have to.
This guide is for VPs of IT, data architects, and migration leads at companies moving data from Relativity to iManage — whether you're scoping, planning, or mid-program.
Relativity stores litigation documents in workspaces with fields, layouts, coding decisions, and production sets optimized for document review. iManage organizes documents in client/matter workspaces with metadata profiles, version control, and security designed for ongoing document management. Settle translates Relativity's review-centric data to iManage's management-centric model — preserving the metadata investments made during eDiscovery.
Based on the founding team's enterprise migration experience
Last updated July 2026
How Settle automates your Relativity to iManage migration
Settle translates Relativity's eDiscovery metadata to iManage's document management profile attributes — mapping responsiveness coding, privilege designations, and issue tags to iManage custom fields that preserve the review investment.
Document selection criteria are generated from Relativity coding fields — Settle identifies which documents should migrate (key, responsive, privileged, work product) vs. which should be archived or disposed based on your matter close policy.
Production Bates numbers are preserved as iManage profile attributes — so documents remain searchable by production number in the DMS for ongoing litigation reference.
Settle maps Relativity's folder structure to iManage's workspace organization and proposes restructuring where review-centric groupings should be replaced with management-centric filing.
Get your Relativity to iManage mapping analysis — see results in under an hour
Migration timeline: manual vs. Settle
Traditional approach
Timeline
1–3 months
Estimated cost
$75K–$250K
Team size
1–3 litigation support specialists
Typically requires
×Manual field mapping in spreadsheets
×Custom ABAP/SQL extraction scripts
×3–5 mock migration cycles
×Dedicated source system consultants
×Manual reconciliation testing
With Settle
Enterprise benchmarksTimeline
Days
Estimated cost
A fraction of consulting cost
Team size
1 internal resource
Included
✓Schema profiling & analysis
✓AI-generated field mappings
✓Transformation SQL
✓Validation & readiness reports
✓Production-ready load files
Common challenges migrating from Relativity to iManage
eDiscovery metadata to document management metadata
Relativity workspaces contain eDiscovery-specific fields — Responsiveness, Privilege, Issue Coding, Confidentiality Designation, Production Bates Numbers. iManage uses document management metadata — document type, author, practice area, security class. Settle maps Relativity's review-specific fields to iManage's management-specific profile attributes, preserving the review investment as document metadata.
Explore related migrations →Document selection and scope
Not all Relativity documents should migrate to iManage — typically only key documents (responsive, hot, privileged), work product (privilege logs, production sets, review outlines), and attorney notes move to the DMS. The rest is archived or disposed per retention policy. Settle generates selection criteria based on coding fields and tags to define the migration scope.
Explore related migrations →Production numbering and Bates stamps
Relativity tracks production numbers (Bates stamps) across multiple production sets. These identifiers are critical for ongoing litigation reference and must be preserved in iManage. Settle maps production numbers to iManage custom profile fields so documents remain findable by Bates number in the DMS.
Explore related migrations →Workspace structure to iManage filing
Relativity workspaces use folders, saved searches, and views for document organization. iManage uses workspace folders with different structural patterns. The organizational structure that made sense for review may need restructuring for long-term management. Settle maps Relativity's folder structure to iManage's workspace tabs and proposes reorganization where review-specific groupings don't serve management needs.
Explore related migrations →Relativity to iManage field mapping — what data moves
10 data objects typically migrated
| Source Object | → | Target Object |
|---|---|---|
| Workspace | → | Workspace (client/matter) |
| Document (native) | → | Document |
| Document (produced/redacted) | → | Document (production version) |
| Responsiveness Coding | → | Custom profile attribute |
| Privilege Designation | → | Security class / Custom attribute |
| Issue Coding / Tags | → | Custom profile attributes |
| Production Bates Number | → | Custom profile field |
| Folder Structure | → | Workspace folders |
| Privilege Log | → | Work product document |
| Review Notes / Comments | → | Document annotations / Notes |
Typical enterprise migrations include 500K–10M+ records across these objects. Settle handles profiling and mapping at enterprise scale.
The cost of manual Relativity to iManage migration
Relativity to iManage migrations happen when litigation work products need to move from the eDiscovery review platform to the firm's permanent document management system. After document review is complete — responsiveness decisions made, privilege logs built, productions completed — the key documents and work product must be preserved in iManage for long-term access, records retention, and matter knowledge management. This is a post-litigation workflow, not a platform replacement.
The migration maps Relativity's eDiscovery workspace structure to iManage's document management model. Relativity organizes documents in workspaces with custom fields (date fields, coding fields, issue tags), saved searches, and production sets. iManage organizes documents in client/matter workspaces with profile attributes, version history, and security. The core challenge is translating Relativity's review-specific metadata (responsiveness coding, privilege designations, production numbering) into iManage's document management metadata.
Litigation support teams and legal IT consultants manage these migrations as part of matter close procedures. The metadata translation, production document selection, and security classification are the key decision points.
Consulting-led delivery for migrations in this class typically runs $75K–$250K. Settle prices it fixed and scoped — read the full cost breakdown.
Frequently asked questions
Related migration paths
Exceptions surface before the first load, not after the third.
Built by the team that ran Fortune 500 migrations by hand. Currently onboarding enterprise design partners on active migration programs.
Ready to migrate from Relativity to iManage?
Tell us about your migration and we'll show you how Settle can help.
No commitment required. We'll review your migration scope and share a preliminary assessment within 48 hours.