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

Data migration route

Doc.It Suite to Filevine migration

Doc.It Suite is a document management system for accounting firms, and Filevine is a cloud case management system. The move is matching each file in Doc.It Suite to its case in Filevine.

FromDoc.It SuiteDocument management
  1. Matters: Carried across
  2. Documents: Carried across
  3. Tasks: Carried across
  4. Contacts: Confirmed in the analysis
  5. Emails: Confirmed in the analysis
  6. Notes: Confirmed in the analysis
  7. Calendar: Confirmed in the analysis
  8. Custom fields: Confirmed in the analysis
  9. Templates: Confirmed in the analysis
ToFilevineCloud
  • 3 carried
  • 6 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Doc.It Suite to Filevine

Each row is a kind of record Doc.It Suite holds, whether Filevine has a place for it, and what is planned. On this route three kinds of record carry across and six kinds are confirmed in the analysis.

Records in Doc.It Suite and their place in Filevine
RecordIn Doc.It SuiteIn FilevineWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partEngagements are organised as client Work Binders, not as legal matters.Has a placeLoaded as projects of a defined project type.Carried across
ContactsClients, other parties and referrersTo be confirmedHas a placeContact cards, linked to projects.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 placeDocs section with folders. Templated project folders can be set per type.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeHeld in the activity feed of the project.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeHeld as notes in the activity feed.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeDeadlines and calendar events.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partWork Binders carry status, due dates and routing between staff.Has a placeCarried across
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCustom sections and fields per project type.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt as Filevine document templates. They are not converted.Confirmed in the analysis

What the plans mean

Carried across
Filevine 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.

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

Every document goes to the case it belongs to.

A case management system expects each document to sit on a case, usually in a category such as correspondence, medical records or court documents. Doc.It Suite organises files its own way, by profile or by folder. So the move needs two rules: which case a file belongs to, and which category it goes in. The first comes from client and matter references or folder names. The second comes from a document type or a subfolder, and where neither exists the files arrive uncategorised and are marked as such.

Cases must exist in Filevine before documents can be attached to them. If the system is already live, files are matched to its case list and the unmatched ones are reported. If it is new, the case list is created first. Dates, authors and file names are kept. Email comes across as message files. Where several versions of a document exist, the firm chooses between loading the latest and loading them all.

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. Doc.It Suite runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Filevine is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.

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

Loading a firm into Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.

  1. Project types before data

    Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.

  2. One contact card per person

    Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.

  3. Lists become collection items

    Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.

  4. History goes into the feed

    File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.

  5. Billing is a separate switch

    The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.

More about moving into Filevine

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Filevine 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 Filevine. 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 Filevine 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 toFilevine

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 Filevine. 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

Setting up Filevine

Loaded data is not yet a working system. This is what NewLaw sets up in Filevine, beyond the migration, so that people can work in it from the first day.

Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.

Set-up decisions in Filevine

  • Design project types, sections and fields for each practice area
  • Define phases and the tasks each phase should trigger
  • Build document templates that fill from project fields
  • Set teams, permissions and protected sections for restricted matters
  • Decide whether Billing and Payments are switched on
  • Connect Lead Docket so signed leads become projects

Questions

Doc.It Suite to Filevine: 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 Filevine?

Filevine stores documents. Docs section with folders. Templated project folders can be set per type. 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.

Does everything in Doc.It Suite have a place in Filevine?

Most of it does on paper. Contacts, emails, notes, calendar entries, custom fields and templates could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Filevine is kept as a readable archive, and you see which before the move.

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

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 Filevine are the names and marks of their owners, used here only to identify the two systems.

Moving from Doc.It Suite to Filevine?

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

We reply within one business day.