iManage to NetDocuments_

No native integration exists between iManage and NetDocuments. These are the two dominant document management systems in the legal sector — iManage serving primarily on-premise and hybrid deployments, NetDocuments offering a fully cloud-native alternative. Firms transitioning from iManage to NetDocuments (or maintaining both during a migration) need a custom pipeline that preserves metadata, version history, security permissions, and folder structures. Formulaic builds these migration and coexistence workflows.

Short answer: No native iManage-to-NetDocuments integration exists. Formulaic builds migration pipelines that preserve metadata, version history, and folder structures during DMS transitions.

What data moves between iManage and NetDocuments

The migration transfers documents with their full metadata. Document files — Word documents, PDFs, emails, spreadsheets, images — move from iManage workspaces to NetDocuments cabinets. Every document carries its profile attributes: document type, author, creation date, last modified date, matter reference, client name, and custom metadata fields.

Version history transfers completely. Every version of every document — from initial draft through final — moves to NetDocuments with the correct timestamps and author attributions. This is critical for firms where document history has regulatory or litigation significance.

Workspace structure maps to NetDocuments cabinet and folder organisation. iManage’s workspace hierarchy translates to NetDocuments’ cabinet-workspace-folder structure. The mapping is not always one-to-one, so the migration includes a structure design phase where the firm decides how iManage’s organisation translates to NetDocuments’ model.

Security permissions transfer from iManage security groups to NetDocuments access control. Ethical walls, confidentiality restrictions, and team-based access all carry across. This is the most sensitive part of the migration — getting permissions wrong creates compliance risk.

Email filing records — the connection between filed emails and their workspace — transfer as document links in NetDocuments, maintaining the correspondence history within each matter’s documents.

Current workarounds

Without a migration tool, firms either stay on iManage (accepting the higher infrastructure costs) or attempt a manual migration — which at any meaningful document volume is impractical. A firm with 500,000 documents cannot manually transfer and re-profile each one.

Some firms use third-party migration tools from DMS vendors. These handle the bulk transfer but often lack the customisation needed for firm-specific metadata mapping and security permission translation.

The most common scenario is a firm that has decided to move to NetDocuments for cloud-native benefits (reduced infrastructure costs, anywhere access, modern API) but needs a reliable migration that does not disrupt operations during the transition period.

What Formulaic builds

Formulaic builds a migration pipeline and coexistence layer between iManage’s Work Server API and the NetDocuments API. The project runs in four phases.

Phase 1: Assessment and mapping. The system inventories the iManage environment — document counts, workspace structures, metadata fields, security groups, and version history volumes. The firm defines how iManage structures map to NetDocuments: which workspaces become cabinets, how metadata fields translate, and how security groups align.

Phase 2: Pilot migration. A subset of workspaces (typically one practice area) migrates first. The firm validates that documents, metadata, versions, and permissions transferred correctly. Adjustments are made before the full migration proceeds.

Phase 3: Full migration. The system transfers all remaining workspaces in scheduled batches, typically running overnight to minimise operational impact. Progress dashboards show completion status, error counts, and estimated time remaining.

Phase 4: Coexistence and cutover. During the transition period, both systems remain operational. New documents can be created in either system, with sync maintaining alignment. When the firm is ready, iManage access transitions to read-only, and NetDocuments becomes the primary DMS.

Formulaic’s deployment data from DMS migration projects shows an average migration rate of 50,000-75,000 documents per day, with 99.7%+ metadata fidelity across transferred documents.

DIY vs Zapier vs custom build

	DIY / Manual	Zapier / Make	Formulaic Custom Build
Setup time	Months	Not available	4-8 weeks
Cost	Staff time	N/A	Custom-scoped
Data accuracy	Metadata loss	N/A	99.7%+ fidelity
Customisation	None	N/A	Full — mapping, security, structure
Compliance	Risk of permission errors	N/A	Security audit included
Maintenance	Ongoing	N/A	60-day warranty

Timeline and investment

Every build is scoped and priced based on complexity. Simpler data syncs take less time than multi-system orchestration with compliance requirements. Start with an audit to get a clear proposal.

FAQ

Can I migrate from iManage to NetDocuments? Yes. A custom migration pipeline transfers documents, metadata, versions, and permissions. There is no native tool for this.

How long does the migration take? Four to eight weeks depending on volume. 500,000 documents typically takes 6-8 weeks including testing.

How much does a DMS migration cost? Every integration is custom-scoped based on your firm’s requirements. Start with an audit for a clear picture of cost and timeline.

Does it preserve version history? Yes. All document versions transfer with timestamps, author information, and metadata preserved.

Can both systems run during migration? Yes. Coexistence workflows keep both operational during the transition period.

Does it handle security permissions? Yes. iManage security groups map to NetDocuments access controls. Ethical walls transfer correctly.

What about email filing records? Filed emails transfer as documents within the workspace structure, maintaining the correspondence history for each matter.

Can I migrate back if needed? The pipeline is reversible. Documents can be migrated back to iManage if the firm decides to return, though this scenario is rare in practice.