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

Data migration route

Doc.It Suite to Server drives migration

Doc.It Suite is a document management system for accounting firms, and Server drives are plain files on equipment the firm controls. Storage only has folders, so the move decides what of each document’s profile is kept in names and what in an index.

FromDoc.It SuiteDocument management
  1. Documents: Carried across
  2. Contacts: Confirmed in the analysis
  3. Emails: Confirmed in the analysis
  4. Notes: Confirmed in the analysis
  5. Calendar: Confirmed in the analysis
  6. Custom fields: Confirmed in the analysis
  7. Templates: Confirmed in the analysis
ToServer drivesFiles
  1. Matters: Kept as a readable archive
  2. Tasks: Kept as a readable archive
Readable archiveNo place in Server drives
  • 1 carried
  • 6 to confirm
  • 2 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Doc.It Suite to Server drives

Each row is a kind of record Doc.It Suite holds, whether Server drives have a place for it, and what is planned. On this route one kind of record carries across, two kinds have no place in Server drives and are archived and six kinds are confirmed in the analysis.

Records in Doc.It Suite and their place in Server drives
RecordIn Doc.It SuiteIn Server drivesWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partEngagements are organised as client Work Binders, not as legal matters.No placeA matter becomes a folder; its details survive only in an index file.Kept as a readable archive
ContactsClients, other parties and referrersTo be confirmedNo placeCan be kept only as an exported spreadsheet.Confirmed in the analysis
DocumentsFiles stored in or linked from the systemHeldHeld in the Inbox, in Work Binders and in the Archive, named by the firm’s policy.Has a placeFiles in folders, named and dated during the load.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs .msg or .eml files in each matter’s correspondence folder.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs a text or PDF file per matter, not as separate records.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedNo placeConfirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partWork Binders carry status, due dates and routing between staff.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedNo placeConfirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partPrecedents as Word files; merge fields tied to the old system stop working.Confirmed in the analysis

What the plans mean

Carried across
Server drives has a place for this kind of record. It is loaded there and checked against Doc.It Suite.
Confirmed in the analysis
We could not confirm this from the two products’ own material, so it is checked against your data before the plan is fixed.
Kept as a readable archive
Server drives has no place for it. It is exported in a format that opens without Doc.It Suite and handed to the firm as a read-only archive.

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

Profiles flatten into folders and an index.

A document management system knows things about a file that a folder cannot hold: its profile, its versions, who may open it. Moving from Doc.It Suite to Server drives flattens that. Client and matter become folder levels. Document type may become a subfolder. Versions become separate files with a suffix, or only the latest is kept. Each of these is a choice the firm makes before the export, and the result is tested on a sample of real matters.

What the folders cannot carry goes into an index: a spreadsheet listing every exported file with its document number, author, dates, type and original location. With it, a document cited by number in an old email can still be found. Access restrictions do not transfer by themselves. Restricted workspaces are exported to separate folders, and permissions are set on those in Server drives before anyone else is given access.

How Doc.It Suite is run at the firm is settled at the start of the analysis, because its maker’s own material does not settle it. The usual arrangement is assumed here. 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 Doc.It Suite stays untouched until the copy in Server drives has been checked.

Where the data is now

Doc.It was designed around the way an accounting engagement runs, so its content is in one of three states: waiting in the Inbox, live in a Work Binder, or filed in the Archive. A move has to collect all three. For binders it also has to settle whether work in progress is finished first or carried across part-way through, with its status.

  1. Inbox, binders and archive

    Documents in the Inbox have not been filed yet and may belong to nobody. Work Binders hold current engagements with status and routing. The Archive holds the settled record. Each is exported and counted on its own. The Inbox is best emptied by the firm before the freeze, because unrouted scans have no client attached.

  2. Policy Manager names the files

    File names and storage locations follow a firm-wide policy applied as documents are gathered. That helps: the client, year and document type can often be read back out of the name and path. The policy is obtained first and tested against real files, since it may have been revised more than once.

  3. Engagements are not matters

    Accounting work recurs by client and year: a tax return for one year, an audit for the next. A legal system expects matters. The mapping decides whether each client becomes one continuing matter with year folders, or one matter per engagement. That choice changes the matter count considerably and is agreed before the trial load.

  4. Files from other programs

    The Inbox can pass documents on to other binder systems such as CaseWare, and Doc.It works beside tax and practice software. Files produced by those programs open only in them. They are carried across as they are, and the firm confirms it will keep the software needed to read them.

  5. Where it is installed

    The suite has been offered on-premise, hosted and as a hybrid of the two, so the documents may be on the firm’s own server or with a provider. Finding out which, and who can give read access, is the first practical step, ahead of any discussion about mapping.

More about moving off Doc.It Suite

Where it is going

Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.

  1. Agree the tree and the names

    A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.

  2. Budget the path length

    Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.

  3. Dates have to be set deliberately

    A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.

  4. Emails become message files

    Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.

  5. Keep an index beside the files

    A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.

More about moving into Server drives

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Server drives on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Doc.It Suite holds and how it is organised, then agree with you where each kind of record will sit in Server drives. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into Server drives and checked against Doc.It Suite: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in Doc.It Suite, a final pass over a weekend picks up what changed since the trial. Doc.It Suite is kept read only as the fall-back record.

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

Start

Start this migration

Tell us what is in Doc.It Suite 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 fromDoc.It Suite
Moving toServer drives

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 Doc.It Suite holds

    What is in it, how its records link, and where each piece would sit in Server drives. 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

Server drives are storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

A server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.

What is agreed and set up

  • Share and top-level folders for clients, precedents and administration
  • Security groups and folder permissions, with restricted matters separate
  • Drive letter mapped for every user at sign-in
  • Backup schedule and shadow copies for earlier versions
  • Written naming rule for client, matter and document names
  • Read-only area for closed matters and archived system exports

Questions

Doc.It Suite to Server drives: what firms ask

Is Doc.It Suite still a current product now that IRIS owns it?

IRIS acquired Doc.It in 2021 and its website still refers to existing IRIS Doc.It customers. It also sells a newer cloud product, IRIS Document Management, which it says is available to those customers. Whether to stay, take that, or go elsewhere is the firm’s decision. The extraction approach does not change.

Can archived client files go into a legal document system?

Yes, as documents filed under a client and a matter. The Archive’s structure, whatever the firm’s policy made it, is mapped to the destination’s folders or profile fields. What will not carry over is workflow status. Open work is either completed before cutover or listed for the firm to set up again as tasks.

Do documents from Doc.It Suite keep their folders and dates in Server drives?

Server drives store documents. Files in folders, named and dated during the load. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.

What happens to records Server drives have no place for?

On this route that is matters and tasks. They are exported from Doc.It Suite in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

What has to be decided before Doc.It Suite data is loaded into Server drives?

Contacts, emails, notes, calendar entries, custom fields and templates are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.

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

Doc.It Suite and Server drives are the names and marks of their owners, used here only to identify the two systems.

Moving from Doc.It Suite to Server drives?

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

We reply within one business day.