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

Data migration route

Worldox to Litify migration

Worldox is a server-based document management system, and Litify is a cloud case management system. The move is matching each file in Worldox to its case in Litify.

FromWorldoxServer
  1. Matters: Carried across
  2. Documents: Carried across
  3. Emails: Carried with mapping
  4. Custom fields: Carried with mapping
  5. Templates: Carried with mapping
  6. Notes: Confirmed in the analysis
  7. Tasks: Confirmed in the analysis
ToLitifyCloud
  • 2 carried
  • 3 mapped
  • 2 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Worldox to Litify

Each row is a kind of record Worldox holds, whether Litify has a place for it, and what is planned. On this route two kinds of record carry across, three kinds need mapping and two kinds are confirmed in the analysis.

Records in Worldox and their place in Litify
RecordIn WorldoxIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partClient and matter exist as coded profile fields with descriptions, not as matter records.Has a placeMatters, by case type.Carried across
DocumentsFiles stored in or linked from the systemHeldOrdinary files on the network, named by an eight-digit Doc ID, each with a profile.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeldOutlook messages and attachments are profiled and saved to cabinets like other documents.Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Carried with mapping
NotesFile notes, matter notes and contact notesHeld in partEach profile has a comments field of up to 5,000 characters.To be confirmedConfirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldEach cabinet has its own profile form and field tables, set up by the firm.Has a placeCustom fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partPrecedents are kept as documents, often in a cabinet of their own.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping

What the plans mean

Carried across
Litify has a place for this kind of record. It is loaded there and checked against Worldox.
Carried with mapping
Litify 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

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. Worldox 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 Litify 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.

Worldox 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. Litify 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

Worldox documents are real files in real folders on the firm’s network, which makes them easy to reach and easy to misread. The folder path encodes the client and matter codes, the file name is a number, and the description users see is kept by Worldox, not in the file name. A move reads all three together, so each file arrives with its title, matter and author.

  1. File names are numbers

    Worldox numbers documents consecutively and uses the eight-digit Doc ID plus the extension as the file name. Copy a matter folder to another drive and you get files called 00123456.docx with no titles. The description, up to 128 characters, comes from the profile, and the migration names each file from it.

  2. The path is the profile

    Each cabinet has a base path, and the client, matter and document type chosen on the profile form decide the folder beneath it. Reading a path back gives the codes. The field tables give what the codes mean. Both are needed, because a folder called 004417 says nothing until the table says which client that is.

  3. Cabinets differ from one another

    A site can have up to 150 cabinets and each has its own set of fields. One may file by client and matter, another by department and year, and a legacy cabinet may hold documents kept from an earlier system for reference only. Every cabinet gets its own mapping.

  4. Versions, archive and legal hold

    Earlier versions of a document are kept and listed with it, and cabinets can have Archive and Legal Hold areas for documents moved out of the active tree. Whether each of these comes across is a scope question. The file counts in the analysis are split into current, versions, archived and held.

  5. Security lives in two places

    Access is set by Worldox administrators in WDADMIN, by cabinet and by folder, which is how ethical walls are built. Individual files can also be given their own security when profiled. The Windows permissions on the share do not tell the whole story, so restrictions are read from Worldox itself.

More about moving off Worldox

Where it is going

Loading a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.

  1. The design comes first

    Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.

  2. One party, many roles

    Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.

  3. Open enquiries load as intakes

    Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.

  4. Documents load after records

    Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.

  5. Validation rules reject bad rows

    A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.

More about moving into Litify

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Litify on this route, which makes it repeatable: a load can be run again until it is right. The maker of Litify 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 Worldox and checking each trial against Worldox.

  1. Analysis

    We read what Worldox holds and how it is organised, then agree with you where each kind of record will sit in Litify. 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 Litify and checked against Worldox: 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 Worldox, a final pass over a weekend picks up what changed since the trial. Worldox 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 Worldox 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 fromWorldox
Moving toLitify

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 Worldox holds

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

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

A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.

Set-up decisions in Litify

  • Define intake questionnaires and the rules for conversion
  • Set case types, matter stages and page layouts
  • Build matter plans that create tasks at each stage
  • Design document folders and generation templates per case type
  • Configure user roles and sharing for restricted matters
  • Decide on timekeeping, billing and accounting integrations

Questions

Worldox to Litify: what firms ask

Can we just copy the Worldox folders to the new system?

The files will copy, but they will be named with eight-digit numbers and sit in folders named with codes. The descriptions, authors, document types and comments are in the profiles. A proper move pairs each file with its profile first, then names it and files it by matter in the destination.

Do our Doc IDs carry over?

The new system will give each document its own identifier. The Worldox Doc ID can be kept in a field or added to the document name, which is worth doing where the firm prints Doc IDs in document footers. Whether it is searchable afterwards depends on the destination and is confirmed in the analysis.

What about emails saved into Worldox?

They were saved with a profile in the same way as documents, so they move with the matter. In the destination they should arrive as emails, with sender and date readable, not as attachments nobody can sort. The trial load is where that is checked, on a sample of matters with heavy correspondence.

Do documents from Worldox keep their folders and dates in Litify?

Litify stores documents. Loaded to the document component and attached to matters. 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 Worldox have a place in Litify?

Most of it does on paper. Notes and tasks 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 Litify is kept as a readable archive, and you see which before the move.

What has to be decided before Worldox data is loaded into Litify?

Emails, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes and tasks 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

Worldox and Litify are the names and marks of their owners, used here only to identify the two systems.

Moving from Worldox to Litify?

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

We reply within one business day.