Document management migration

NetDocuments to iManage Migration Checklist

NetDocuments to iManage migration checklist: inventory, workspace and security mapping, metadata fidelity, test runs, cutover, validation and rollback.

Direct answer

A NetDocuments to iManage migration checklist should cover inventory of workspaces, cabinets, documents and versions; mapping of profile metadata, security and ethical-wall rules; handling of email, links, checked-out items and external shares; repeated test migrations with reconciliation counts; a frozen cutover window; user validation; rollback criteria; and a defensible retention period before the source system is decommissioned.

How CaseDocker helps

Before swapping one DMS for another, consider consolidating documents, matters, contracts, deadlines and notices in one workdesk. CaseDocker supports this alternative path with bulk import, folders and file history, matter-level members and roles, and audit trails. It does not include an iManage or NetDocuments connector or one-click migration, so this checklist remains the right tool for a direct move.

See it in CaseDocker

Definitions

Source inventory

A counted and sampled record of what exists in the source system, including cabinets, workspaces, folders, documents, versions, email items, shares, users, groups, and storage volume, used as the baseline for every later reconciliation.

Metadata mapping

A documented crosswalk from each source profile attribute, such as client, matter, author, document type, and status, to the target attribute, including value translations and rules for blanks and unmapped values.

Security mapping

The translation of source permissions, groups, matter-level restrictions, and ethical walls into the target access model so that no document becomes more widely visible than it was.

Version fidelity

The degree to which document history, version numbers, authorship, timestamps, and comments arrive in the target as they existed in the source.

Reconciliation

A comparison of counts, checksums, metadata values, and security results between source and target that shows whether each migration run is complete and accurate.

Cutover

The controlled point at which users stop working in the source, final delta content is moved, and the target becomes the system of record.

Rollback criteria

Pre-agreed conditions under which the firm reverts to the source system rather than continuing with a failing cutover.

Delta migration

A final pass that moves only content created or changed since the last full migration run, used to close the gap at cutover.

Workspace

A container for a client or matter and its folders and documents, whose structure and security usually need to be recreated or mapped in the target.

Checked-out item

A document locked for editing in the source system, which can block or distort migration unless it is checked in or handled by rule.

Link remediation

The work of redirecting or rewriting document links embedded in email, notes, and other systems so they resolve in the target.

Migration exception log

A record of every item that failed, was skipped, or was altered during migration, with cause, owner, and resolution.

Practical workflow

  1. Confirm scope, ownership, and success criteria

    Name an executive sponsor, a migration lead, records and risk owners, and a workstream for each of security, metadata, email, integrations, and training. Define what counts as success, including completeness thresholds you set yourself, acceptable downtime, and which content is out of scope such as expired matters or content already scheduled for disposal.

  2. Inventory the source and clean before moving

    Count cabinets, workspaces, folders, documents, versions, and email items, and sample the data for orphaned content, duplicates, corrupt files, blank profile fields, unusually long names, and unsupported file types. Decide which content should be remediated, archived, or disposed of under the retention schedule before it is migrated, but never dispose of content under a legal hold.

  3. Map metadata and structure

    Build the crosswalk from source profile fields, workspaces, folders, and document classes to the target structure. Record value translations, default values for blanks, treatment of inactive clients and matters, and how folder hierarchies and naming conventions will be preserved or normalised. Have practice and records owners approve the map before test runs.

  4. Map security, ethical walls, and external access

    List source groups, matter-level permissions, restricted workspaces, ethical walls, and external shares, then define how each is represented in the target. Treat any mapping that could widen visibility as a defect. Plan for default access on newly created target workspaces, and decide how shared links and guest access will be reissued or retired.

  5. Decide how email, links, and integrations are handled

    Identify how email is filed and referenced, how document links embedded in other systems and in emails will resolve after the move, and which integrations call the source, such as practice management, billing, intake, and Outlook or Office add-ins. Plan link redirection or rewriting, reconfigure each integration, and test them against migrated content.

  6. Run repeated test migrations and reconcile

    Migrate a representative pilot, then progressively larger sets, reconciling counts, checksums where available, version histories, metadata values, and permissions on every run. Log each exception with a cause and fix, adjust the mapping, and rerun until results are stable. Include large files, deep folder paths, special characters, checked-out items, and encrypted or password-protected documents in the pilot.

  7. Plan cutover, communications, and training

    Choose a cutover window that avoids filing deadlines and closings where possible, announce a content freeze, migrate the final delta, and switch integrations. Prepare short role-based training, a floor-walking or help-desk plan, and a way for users to report missing or misfiled documents quickly. Confirm rollback criteria and the decision-maker before the window opens.

  8. Select and contract the migration approach

    Decide whether to use vendor tooling, a specialist provider, or internal scripts, and compare how each handles metadata, versions, security, and email. Put data-handling, confidentiality, and sub-processor terms in writing before any client data is exported.

  9. Prepare the target environment

    Configure the target structure, document classes, metadata fields, security model, retention settings, and integrations before test runs, so results measure the mapping rather than an unfinished environment.

  10. Freeze scope changes and manage holds

    Agree a date after which structural changes in the source stop, and confirm that content under legal hold is identified and preserved in both systems throughout the project.

  11. Validate with users and close out the source

    Ask matter teams to verify a defined set of their own matters, including recent versions, email, and restricted workspaces. Keep the source read-only for an agreed period, retain the migration logs and reconciliation evidence, confirm legal holds and retention are intact in the target, and decommission the source only after the data owner signs off and any contractual export or deletion obligations are met.

Comparison

Migration areaControlled migrationLift-and-hope migration
Inventory and cleanupCounts, samples, and cleanup decisions are recorded before any content moves, with holds respected.Everything is copied as is, including duplicates, orphaned items, and content that should have been disposed of.
MetadataA signed-off crosswalk handles value translation, blanks, and inactive records.Fields are mapped by name only, so values land in the wrong attributes or are lost.
SecurityPermissions and ethical walls are mapped and tested so visibility is never wider than before.Default target access is left in place and restrictions are rebuilt by hand after go-live.
Versions and emailVersion history, authorship, and filed email are reconciled against the source.Only the latest version is moved and email references break silently.
TestingSeveral reconciled test runs precede cutover, and exceptions are fixed in the mapping.A single trial run is treated as proof, and defects surface in production.
Cutover and rollbackA freeze, delta migration, and pre-agreed rollback criteria govern the switch.Users keep working in both systems and nobody owns the decision to revert.
Tooling and providerCapabilities, data-handling terms, and confidentiality obligations are verified before export.A provider is engaged on price alone and handles client data under informal terms.
GovernanceA named sponsor, lead, and workstream owners track decisions and exceptions.Responsibility is spread across IT and practice groups with no single owner.

Limitations and exceptions

  • Export and import capabilities, supported object types, rate limits, and API behaviour differ by product, edition, and version, so verify each against current vendor documentation and your contract before fixing a plan or timeline.
  • Some source features may have no direct equivalent in the target, such as particular workspace types, sharing constructs, or workflow rules, and may need redesign rather than migration.
  • Security and ethical-wall mapping is only as accurate as the source permissions; stale or inconsistent source access will be reproduced or exposed during migration and should be reviewed first.
  • Reconciliation proves what moved, not that the content was correctly classified or complete in the source. Records and practice owners remain responsible for those judgments.
  • Legal holds, client retention instructions, and regulatory obligations may restrict deletion and cleanup. Confirm requirements with counsel and records owners before disposing of any content or decommissioning the source.
  • This checklist is general guidance and not a vendor-endorsed procedure. Engage the vendors, an experienced migration provider, or your internal specialists for product-specific tooling and support.

Primary sources

Methodology

This checklist was assembled from common document-management migration practice and public records-management and security references. It does not rely on vendor benchmarks, and it deliberately avoids stating throughput or completeness figures because they depend on the environment. Teams should adapt the steps to their own contract terms, data volumes, and regulatory obligations, and confirm current product capabilities with each vendor.

Contact

Plan a document migration you can verify

Reach out and learn more about our offerings and how CaseDocker can help you

Built for legal operations teams

Share your use case and we will connect you with the right team for product guidance, pricing, and rollout planning.

Clear next steps

Expect a response from our team with the most relevant next step for your inquiry.

Send us a message

Get in touch

We usually reply quickly

Still needed: name, work email, phone, subject, message

Your message goes directly to our team.

FAQs

Cover scope and owners, a counted source inventory, cleanup decisions, metadata and structure mapping, security and ethical-wall mapping, email and link handling, integration reconfiguration, repeated reconciled test runs, a frozen cutover with rollback criteria, user validation, and a retention period before source decommissioning.

It depends on the tooling, product versions, and configuration. Treat version fidelity and email references as explicit test cases, reconcile them in every pilot run, and confirm supported behaviour with the vendors rather than assuming it.

Map permissions and ethical walls before content moves, ensure target workspaces default to restricted rather than open, test with users who should and should not have access, and treat any widening of visibility as a defect that blocks cutover.

Inventory where links are embedded, such as in email, matter notes, and other systems, then plan redirection or rewriting and test sample links after each pilot. Some links may need to be reissued, so communicate this to users before cutover.

Keep it read-only for a period set by your risk owners, contract terms, and validation results. Decommission only after sign-off, confirmation that holds and retention are intact in the target, and secure disposal of source data.

No. It is vendor-neutral and does not describe proprietary tooling. Use it to structure planning and verify capabilities with each vendor or a qualified migration provider.

It depends on volume, complexity of security and metadata, tooling, and how many test cycles are needed. Build the schedule from your own inventory and pilot results rather than a generic estimate.

It is usually worth deciding what to remediate, archive, or dispose of first, because migrating duplicates, orphans, and expired content raises cost and risk. Never dispose of anything under a legal hold.

CaseDocker is not a migration tool between those two systems and has no connector for either. It is an alternative if you decide to consolidate documents, matters and deadlines in one workdesk instead of moving between DMS products.

Related CaseDocker capabilities

Legal case management

Link matters, parties, documents, tasks, permissions, and activity history in one controlled case workspace.

Explore

Contract management

Keep executed agreements, versions, and metadata in a searchable repository tied to renewals and obligations.

Explore

Compliance management

Track retention, access reviews, and evidence required to show a migration preserved control.

Explore

Legal playbooks

Run migration validation and sign-off steps through repeatable, assigned workflow rules.

Explore

Turn this guide into an operating plan

Share your current legal workflow and CaseDocker can map the right modules, integrations, controls, and rollout sequence.

Book a walkthrough