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

Data migration route

Zoho WorkDrive to Litify migration

Zoho WorkDrive is cloud file storage, and Litify is a cloud case management system. The move is matching each file in Zoho WorkDrive to its case in Litify.

FromZoho WorkDriveCloud
  1. Documents: Carried across
  2. Emails: Carried with mapping
  3. Custom fields: Carried with mapping
  4. Templates: Carried with mapping
ToLitifyCloud
  • 1 carried
  • 3 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Zoho WorkDrive to Litify

Each row is a kind of record Zoho WorkDrive holds, whether Litify has a place for it, and what is planned. On this route one kind of record carries across and three kinds need mapping.

Records in Zoho WorkDrive and their place in Litify
RecordIn Zoho WorkDriveIn LitifyWhat is planned
DocumentsFiles stored in or linked from the systemHeldFiles in Team Folders and My Folders, including Zoho Writer, Sheet and Show documents.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeld in partOnly messages saved into a folder as files.Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Carried with mapping
Custom fieldsFields and record types the firm added itselfHeld in partLabels and Data Templates attach classification fields to files.Has a placeCustom fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partPrecedents are kept as files, often in Zoho Writer format.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 Zoho WorkDrive.
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.

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. Zoho WorkDrive 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.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Zoho WorkDrive depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Zoho WorkDrive is kept running until the checks on Litify are finished.

Where the data is now

WorkDrive is rarely a firm’s only Zoho product, and the move off it is cleaner when that is faced at the start. The documents are here. Client and matter records that explain them may be in Zoho CRM or another Zoho app. Collecting the files without the records that give them a matter number leaves a tree of folders to be matched by name.

  1. Team Folders and My Folders

    Team Folders are the firm’s and can be listed by an administrator. My Folders are each person’s private space, and matter drafts end up there more often than anyone admits. Staff are asked to move firm documents into the right Team Folder before collection, or to identify the personal folders that should be taken.

  2. Writer, Sheet and Show documents

    Documents created in Zoho’s editors are in Zoho formats. A destination built around Microsoft Word needs them converted to .docx, .xlsx or PDF on the way out. Merge fields, comments and tracked changes are where conversions go wrong, so a sample of the firm’s real precedents is converted and read before the full run.

  3. Labels and Data Templates

    If the firm classified documents with labels or Data Templates, that classification is stored in WorkDrive and not in the file. It has to be exported alongside each document. Where the destination has document types or profile fields, the values are mapped to them. Otherwise they are written into the file name.

  4. Five roles to translate

    Access in a Team Folder is by role: Admin, Organizer, Editor, Commenter or Viewer. Few destinations have the same five. The firm’s actual need is usually simpler, a list of who may open which matters, and that list is drawn from the role assignments and confirmed with a partner.

  5. Unlimited versions, limited use

    Zoho describes version history in WorkDrive as unlimited, so a long-lived precedent may have hundreds of versions. Bringing them all is seldom useful. The firm sets a rule, such as the latest version only for closed matters and the last few for open ones, before volumes are estimated.

More about moving off Zoho WorkDrive

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 Zoho WorkDrive and checking each trial against Zoho WorkDrive.

  1. Analysis

    We read what Zoho WorkDrive 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 Zoho WorkDrive: 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 Zoho WorkDrive, a final pass over a weekend picks up what changed since the trial. Zoho WorkDrive 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 Zoho WorkDrive 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 fromZoho WorkDrive
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 Zoho WorkDrive 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

Zoho WorkDrive to Litify: what firms ask

We also use Zoho CRM for clients. Is that part of the same move?

It should be looked at together even if it is moved separately. The CRM is where client names, contact details and often matter references are held, and WorkDrive folders are usually named after them. Reading both lets each folder be tied to the right client and matter in the new system without guesswork.

Will our Zoho Writer precedents work in Word?

The text and most formatting convert. Automation does not carry over by itself: merge fields that pulled data from Zoho have to be rebuilt against the new system’s fields. Precedents are therefore handled as a small project of their own, starting with the documents the firm uses every week.

Can we keep WorkDrive for closed matters?

Yes, for as long as the subscription runs. The practical points are that at least one current staff member keeps an Admin role on each Team Folder, and that the closed matters are set to view only so nothing is filed there by habit after go-live. Both are checked at handover.

Do documents from Zoho WorkDrive 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 Zoho WorkDrive have a place in Litify?

On paper, yes: each kind of record Zoho WorkDrive holds has a place in Litify. 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 Zoho WorkDrive data is loaded into Litify?

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

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

Moving from Zoho WorkDrive 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.