Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

iManage Work data to Microsoft SQL Server

iManage Work is a server-based document management system, and Microsoft SQL Server is a database on a server the firm runs. What lands in Microsoft SQL Server is the register: every file’s name, place, dates and details, with the files themselves stored beside it.

FromiManage WorkServer
  1. Matters: Exported in full
  2. Tasks: Exported in full
  3. Documents: Exported with mapping
  4. Emails: Exported with mapping
  5. Custom fields: Exported with mapping
  6. Templates: Exported with mapping
ToMicrosoft SQL ServerServer
  • 2 carried
  • 4 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from iManage Work to Microsoft SQL Server

Each row is a kind of record iManage Work holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route two kinds of record carry across and four kinds need mapping.

Records in iManage Work and their place in Microsoft SQL Server
RecordIn iManage WorkIn Microsoft SQL ServerWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partA workspace usually stands for a matter, with client and matter held as custom1 and custom2.Has a placeA table of matters linked to clients, parties and fee earners.Exported in full
DocumentsFiles stored in or linked from the systemHeldEach is identified by its library name, a document number and a version number.Has a place in partAs files in folders with an index table; storing files in the database is possible.Exported with mapping
EmailsEmails saved to matters or to the storeHeldFiled emails are stored as documents, usually in email folders inside the workspace.Has a place in partAs message files with an index table, or as rows of header fields.Exported with mapping
TasksTo-dos and workflow steps assigned to peopleHeld in partTask lists are kept in iManage Tracker, a separate product.Has a placeRows with assignee, due date and status.Exported in full
Custom fieldsFields and record types the firm added itselfHeldCustom profile fields with validated lists, captioned by the firm, such as practice area.Has a placeAs added columns, or a table of field names and values.Exported with mapping
TemplatesPrecedents, document templates and automationHeld in partPrecedents are held as documents. Workspace templates only set folder structure.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping

What the plans mean

Exported in full
Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against iManage Work.
Exported with mapping
Microsoft SQL Server holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.

The table states what the two products hold and what NewLaw plans for. It is not a promise that every record moves: that is settled against your own data in the analysis.

This kind of move

The files, and a register of what each one is.

A database is a poor place to keep documents and a good place to keep facts about them. On this route the files from iManage Work are exported to storage the firm controls, and Microsoft SQL Server receives the register: one row per file, with its path, size, dates, author and whatever profile or folder details existed. That register is what makes a large export searchable. It also proves completeness, since the row count and total size can be agreed to the source.

How useful the register is depends on how much iManage Work knows about each file. A document management system has a profile to carry. A plain folder has only a path and dates, and the client or matter has to be read out of folder names. Where versions or an audit history exist, each becomes a table of its own. The export is checked by picking documents at random in the source, finding them through Microsoft SQL Server, and opening the file to confirm it is the same one.

Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in iManage Work stays untouched until the copy in Microsoft SQL Server has been checked.

Where the data is now

Moving off an on-premises library starts with access to its database and its file store, because the profiles, security and version history are read from the database. The stored files on their own are not usable: each one has to be matched to its profile. Most of the planning goes into client and matter numbers, security, and which versions come across.

  1. The database carries the meaning

    The title, author, client, matter, class and folder location of every document are rows in the library database, not properties of the stored file. An extraction that copies only the file store brings none of that with it. The database and the files therefore have to be collected together, at the same point in time.

  2. Client and matter are custom fields

    Custom1 and custom2 are a parent and child pair, normally captioned Client and Matter, and every value has to exist in a validated list. That list is usually fed from the practice management system. The analysis compares it with the destination’s matter list, since closed or renumbered matters often exist in one and not the other.

  3. Document numbers get quoted

    A document is identified by library, number and version, and lawyers quote those numbers in emails, footers and other documents. The firm decides whether every version moves or only the latest, and whether the old number is kept as a searchable field or in the document name so an old reference can still be traced.

  4. Security is layered

    Each workspace, folder and document has a default security of private, view, public or inherited, and users or groups can be granted or denied access on top of that. Private documents and walled-off matters are either reproduced in the destination or deliberately opened up. That is decided group by group before the trial load.

  5. Emails are documents here

    A filed email is stored as a document in its own right, often in an email folder inside the workspace, and the same message may have been filed by several people. Volumes are large. The trial load reports how many emails each matter holds and how repeated copies were treated.

More about moving off iManage Work

Where it is going

There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.

  1. Restored copy or rebuilt schema

    Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.

  2. No screens come with it

    A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.

  3. Documents sit beside the database

    Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.

  4. The edition follows the size

    A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.

  5. Backups and a test restore

    An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.

More about moving into Microsoft SQL Server

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what iManage Work holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything iManage Work holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to Microsoft SQL Server as a trial and checked against iManage Work: record counts, totals where iManage Work holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in iManage Work, the export is run a final time and checked again. There is nothing to go live. iManage Work is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

Fixed price, agreed after the analysis. How NewLaw moves legal data

Start

Start this migration

Tell us what is in iManage Work and roughly how much of it. The first step is the analysis, and the price is fixed once it is done.

Step 1 of 5

Step 1 of 5: Start with the route

Moving fromiManage Work
Moving toMicrosoft SQL Server

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what iManage Work holds

    What is in it, how its records link, and where each piece would sit in Microsoft SQL Server. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  3. A fixed price in writing

    Set after the analysis, so it reflects what is in your data. You have it before any work starts.

Beyond the data

Structure, permissions and handover

Microsoft SQL Server is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.

What is agreed and set up

  • Server, instance and edition agreed with the IT provider
  • Read-only logins and roles for named staff
  • Views for matter, ledger, time and document look-ups
  • Backup schedule and who tests a restore
  • Plain names and descriptions for tables and columns
  • Excel or Power BI connected for reporting

Questions

iManage Work to Microsoft SQL Server: what firms ask

Can we keep our iManage document numbers?

The number is assigned by the library, so the new system will issue its own. What can be kept is the old number as a reference: in a custom field, in the document name, or in a lookup list. Which is possible depends on the destination, and it is settled in the analysis because footers and old emails quote the numbers.

Do all versions of a document come across?

They can be extracted, since each version has its own profile. Whether the destination keeps them as versions of one document or as separate documents depends on that system. A common choice is every version for open matters and the latest version only for matters that closed some years ago.

Is moving to iManage Cloud the same job as moving to another product?

No. Going to iManage’s own cloud keeps the same structure of libraries, workspaces, profiles and security, and iManage publishes its own resources for that move. Moving to a different product means mapping each of those concepts onto something else, which is where the analysis time goes.

Does the copy in Microsoft SQL Server hold documents from iManage Work?

In part. As files in folders with an index table; storing files in the database is possible. What Microsoft SQL Server can hold is written out once its mapping is agreed, and the rest is kept beside the data as files that open without iManage Work.

Does everything in iManage Work have a place in Microsoft SQL Server?

On paper, yes: each kind of record iManage Work holds has a place in Microsoft SQL Server. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.

What has to be decided before iManage Work is written out to Microsoft SQL Server?

Documents, emails, custom fields and templates are exported with mapping, so each mapping is agreed with you first. The firm also decides who may open the archive and how long it is kept.

Where to start

Before and after the move.

Choosing the system comes before a migration. Setting it up and putting AI to work come after.

How we do itDiscovery to rollout, step by step

iManage Work and Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.

Moving from iManage Work to Microsoft SQL Server?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.