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

Data migration route

Dropbox to Litify migration

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

FromDropboxCloud
  1. Documents: Carried across
  2. Emails: Carried with mapping
  3. Templates: Carried with mapping
  4. Notes: Confirmed in the analysis
ToLitifyCloud
  • 1 carried
  • 2 mapped
  • 1 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Dropbox to Litify

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

Records in Dropbox and their place in Litify
RecordIn DropboxIn LitifyWhat is planned
DocumentsFiles stored in or linked from the systemHeldFiles in folders, synced to desktops, with version history for a set number of days.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeld in partOnly where messages were saved into a folder as .msg or .eml files.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 partDropbox Paper documents, where staff used them for notes.To be confirmedConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partPrecedents are kept as ordinary files in a folder.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 Dropbox.
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. Dropbox 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 Dropbox 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 Dropbox is kept running until the checks on Litify are finished.

Where the data is now

Moving off Dropbox begins with a simple question that often has an awkward answer: whose account are the files in. A team space is one thing. Personal accounts sharing folders with each other are another, and the firm’s matter files may sit partly in an account that belongs to someone who has left.

  1. Team space or personal accounts

    On a team plan, team folders belong to the firm and an administrator can see them all. Outside one, each folder belongs to the person who created it and the others only have it shared to them. The analysis lists every account that owns matter folders, so that none is left behind when subscriptions are cancelled.

  2. Collect from the account itself

    Files marked online-only show in Explorer but are not on the disk. Copying the Dropbox folder from one computer can produce a tree that looks whole and is missing its contents. The files are taken from the Dropbox account itself, and one PC’s folder is used only to check the result.

  3. Conflicted copies

    When two people save the same file at once, Dropbox keeps both and adds the editor’s name and the words conflicted copy to one of them. Years of this leaves matter folders with near-duplicates. They are reported in the clean-up, and the firm decides whether to keep the later file, both, or review them by hand.

  4. Paper docs need exporting

    Dropbox Paper documents are not Word files. Each can be exported to .docx, Markdown or PDF, and on the current release of Paper that is done one document at a time. Where a firm kept file notes or checklists in Paper, they are counted early because the export is manual work.

  5. Version history is a time window

    Dropbox keeps earlier versions for a number of days set by the plan, not for a number of versions. Anything older has already gone. If earlier drafts matter for particular matters, they are pulled out while the window still covers them and before the plan is downgraded or cancelled.

More about moving off Dropbox

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

  1. Analysis

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

Dropbox to Litify: what firms ask

Our files are in a partner’s personal Dropbox. Can they still be moved?

Yes, with the partner’s consent and access to that account. The shared folders are collected from the account that owns them, so nothing depends on what happens to be synced to one laptop. Personal folders mixed in with client folders are marked by the partner beforehand and left out.

Will the dates on our documents change?

The modified date of each file is recorded when it is collected and written to the destination where the destination allows it to be set. Some systems stamp every loaded document with the load date as its created date. The trial load shows which dates the new system displays, checked against a sample of old matters.

What about links we have sent to clients?

Shared links point at files in Dropbox, so they cannot be relied on once those files are removed or the account is closed. A list of active links and shared folders is produced before cutover. The firm then tells the clients concerned where their documents will be available afterwards.

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

Most of it does on paper. Notes 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 Dropbox data is loaded into Litify?

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

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

Moving from Dropbox 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.