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

Data migration route

Doc.It Suite to LexWorkplace migration

Doc.It Suite is a document management system for accounting firms, and LexWorkplace is a cloud document management system. The test of this move is whether profiles, versions and access rules survive it.

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

What moves

What moves from Doc.It Suite to LexWorkplace

Each row is a kind of record Doc.It Suite holds, whether LexWorkplace has a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping and seven kinds are confirmed in the analysis.

Records in Doc.It Suite and their place in LexWorkplace
RecordIn Doc.It SuiteIn LexWorkplaceWhat 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 place in partName, custom ID, client, type, location, staff, tags and dates. No parties or financial fields.Carried with mapping
ContactsClients, other parties and referrersTo be confirmedNo placeOnly a client name, status, attorneys and tags.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 placeFiled to a matter or to Firm Documents, in folders.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeOn the matter’s Email tab, in their own folders.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeAs Matter Notes on the matter’s Notes tab.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.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a place in partOld categories can become document types, statuses or tags.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partStored as files in Firm Documents.Confirmed in the analysis

What the plans mean

Carried across
LexWorkplace has a place for this kind of record. It is loaded there and checked against Doc.It Suite.
Carried with mapping
LexWorkplace holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
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

Profiles, versions and security, kept intact.

Between two document management systems the files are the easy part. What a firm has built in Doc.It Suite is everything around them: the profile on each document, its version history, who can open it, which workspace it sits in. LexWorkplace has its own model for each. Document types and custom profile fields are mapped one to one where they can be. Versions are loaded in order, so the latest in the old system is the latest in the new one.

Security is checked on its own. A restricted client or an information barrier must arrive restricted, so access groups are created in LexWorkplace before any document is loaded, and a sample of restricted workspaces is tested with a user who should not see them. Document numbers are worth keeping, since they appear in footers and old emails. Where the new system assigns its own, the old number is stored as a searchable field.

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

LexWorkplace expects every document and email to belong to a matter, so loading it starts with the matter list: name, custom ID, client, type and dates. Uptime Legal states that it runs migration and onboarding for its customers itself. The preparation is getting the old system’s content into a clean client and matter structure, with the exceptions resolved, ready for that load.

  1. Matters carry little, by design

    A matter record holds a name, a custom ID, a client, a type, a location, assigned staff, tags and open and close dates. Parties, court details and financial data have no fields. Those stay in the practice management system, and the two are tied together by using the same matter number as the custom ID.

  2. Clients are only containers

    LexWorkplace says plainly that its clients are for grouping matters, not for client management. A client has a name, a status, primary attorneys and tags. Addresses, phone numbers and contact history from the old system are not loaded here. They go to the practice management system or stay behind.

  3. Three tabs per matter

    Content arrives as documents, emails or notes, each on its own tab with its own folders. Emails held as message files in an old folder tree have to be recognised and loaded as emails, not as documents, or they will not appear where lawyers look for correspondence.

  4. Closed matters and archive

    A matter is closed by giving it a close date, and closed matters can be moved to archive storage, where they keep their place but are not searched or indexed until un-archived. Old matters can therefore be loaded and archived straight away. The firm sets the cut-off year.

  5. Profiling is optional unless enforced

    Document type, status and tags are not required by default, though a firm can switch on mandatory profiling for matters. If the old system had document types, they are mapped to LexWorkplace types during the load. If it had none, the firm chooses between loading unprofiled and assigning types by folder name.

More about moving into LexWorkplace

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in LexWorkplace on this route, which makes it repeatable: a load can be run again until it is right. The maker of LexWorkplace says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Doc.It Suite and checking each trial against Doc.It Suite.

  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 LexWorkplace. 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 LexWorkplace 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 toLexWorkplace

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

Loaded data is not yet a working system. The maker of LexWorkplace runs or arranges the set-up of its product, so this is what has to be decided and put in place in LexWorkplace, whoever does the work, before people rely on it from the first day.

Setting LexWorkplace up for a firm is a short list of decisions made in its settings, plus software on each computer. The decisions are what the firm calls its matter types, document types and statuses, who can open which matters by default, and whether versioning is automatic or manual. The Launcher and the Outlook add-in are then installed for every user.

Set-up decisions in LexWorkplace

  • Matter types, document types, statuses and tag conventions
  • Groups, rights and default permissions for new matters
  • Automatic or manual versioning, and whether profiling is mandatory
  • Linking matters to Clio Manage where the firm uses it
  • Launcher, Office and Outlook add-ins on each Windows or Mac computer
  • A Firm Documents structure for templates, policies and internal files

Questions

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

LexWorkplace stores documents. Filed to a matter or to Firm Documents, in folders. 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 LexWorkplace?

Most of it does on paper. Contacts, emails, notes, calendar entries, tasks, 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 LexWorkplace 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 LexWorkplace?

Matters are carried with mapping, so each mapping is agreed with you first. Contacts, emails, notes, calendar entries, tasks, 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 LexWorkplace are the names and marks of their owners, used here only to identify the two systems.

Moving from Doc.It Suite to LexWorkplace?

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

We reply within one business day.