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

Data migration route

Local folders to Sync.com migration

Local folders are plain files on equipment the firm controls, and Sync.com is cloud file storage. The folders move as they are, and the work is in permissions, paths and links.

FromLocal foldersFiles
  1. Documents: Carried across
  2. Emails: Carried with mapping
  3. Notes: Carried with mapping
  4. Templates: Carried with mapping
ToSync.comCloud
  1. Time and expenses: Kept as a readable archive
  2. Billing: Kept as a readable archive
Readable archiveNo place in Sync.com
  • 1 carried
  • 3 mapped
  • 2 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Local folders to Sync.com

Each row is a kind of record Local folders hold, whether Sync.com has a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping and two kinds have no place in Sync.com and are archived.

Records in Local folders and their place in Sync.com
RecordIn Local foldersIn Sync.comWhat is planned
DocumentsFiles stored in or linked from the systemHeldFiles in one user’s folders, with no sharing or versions.Has a placeFiles and folders within the path limit; some file types are skipped by the apps.Carried across
EmailsEmails saved to matters or to the storeHeld in partSaved .msg files, and Outlook data files stored under Documents.Has a place in partMessage files such as .msg or .eml, filed in the matter’s folder.Carried with mapping
NotesFile notes, matter notes and contact notesHeld in partFile notes kept as Word documents or text files.Has a place in partOnly as a document written out to the matter’s folder.Carried with mapping
Time and expensesTime and expense entries, billed and unbilledHeld in partTimesheets kept as spreadsheets, where a practitioner works that way.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeld in partInvoices as Word or PDF files; no ledger.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationHeld in partPersonal precedents and Word templates saved by the user.Has a place in partPrecedents load as ordinary files.Carried with mapping

What the plans mean

Carried across
Sync.com has a place for this kind of record. It is loaded there and checked against Local folders.
Carried with mapping
Sync.com holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
Kept as a readable archive
Sync.com has no place for it. It is exported in a format that opens without Local folders and handed to the firm as a read-only archive.

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

Same folders, new home.

Copying folders from Local folders to Sync.com sounds like a drag and drop, and for a few gigabytes it is. For a firm’s whole document store the trouble is in the detail. The two stores have different limits on path length and different rules about characters in file names. Files open on someone’s desk during the copy are skipped. Modified dates are reset unless the copy is made with a tool that preserves them. Each of these is checked on a trial copy first.

Permissions and links do not travel. Who can see which folder is set up again in Sync.com, and it is a good moment to replace access granted to individuals over the years with groups. Shared links sent to clients stop working when the old store is switched off, so the live ones are listed and reissued. Documents that point at other documents by path, common in spreadsheets, are found and reported. The final pass copies only what changed since the trial.

With Local folders the files are already on equipment the firm controls, so there is no export step: they are read where they are. Upload speed sets the pace for a large store. The originals stay in place, unchanged, until the firm has checked the copy in Sync.com.

Where the data is now

Collecting from local folders means going machine by machine, and person by person, because nobody else knows what is there. Volumes are small next to a server drive. The value can be high: the only signed copy of a deed, a partner’s twenty years of precedents, the working files of every matter a sole practitioner has open.

  1. An inventory per computer

    Every PC, Mac and laptop in scope is scanned for documents outside the system folders, including machines kept at home and the one in the storeroom nobody has started in a year. Each user profile on a shared computer is scanned separately. The result is a list by machine that the firm signs off.

  2. Local drafts against the shared copy

    Where the firm also has a server or cloud drive, a local file is often a later draft of something filed there, or an older one. Files are compared by content. Identical copies are dropped, and the differing ones are shown side by side with their dates so the lawyer can say which is current.

  3. Folders that only look local

    A OneDrive, Dropbox or Google Drive folder appears in Explorer like any other, but its contents belong to the cloud account and may not be on the disk in full. Those are collected from the service. Scanning them as local folders double counts files and can copy empty placeholders.

  4. Mail archives under Documents

    Outlook’s default location for data files is an Outlook Files folder inside Documents. A scan for documents will find them, sometimes many gigabytes each. They are set aside and handled as mail, matched to matters by folder and correspondent, not loaded as single enormous files.

  5. One person’s own system

    A lawyer’s local folders follow a private logic: by year, by court, by the other side’s surname. The owner spends half an hour explaining it, and the mapping to matters is written from that conversation. Where the owner has left the firm, folders are matched on client names and dates alone.

More about moving off Local folders

Where it is going

A firm that moves its files to Sync is usually doing so for confidentiality, and the load has to respect how the service is built to deliver it. Files are encrypted before they leave the computer. Nobody at Sync can look inside the account to confirm what arrived, so the checking is done from the firm’s side, against the list of what was sent.

  1. Files or Vault

    Open matters belong in Files, where they sync to the people working on them. Closed matters can go to Vault, which holds them in the cloud without putting a copy on every laptop. The firm supplies its open and closed matter lists so each folder is sent to the right side.

  2. A 248 character path limit

    Sync sets a maximum path length of 248 characters to stay compatible between Windows and Mac, and its apps skip anything longer. That is tighter than most systems a firm will be coming from. Folder names are shortened in the plan, and Sync’s own guidance favours a tree only a few levels deep.

  3. What the apps leave out

    The desktop apps do not upload shortcut files, temporary Office files or names containing a slash, and they warn against several other characters on Windows. A copy to Vault produces a transfer report listing what was skipped. That report is reconciled against the source file list after every load.

  4. Permissions come from the top folder

    Sharing is set on a folder and flows down to all of its contents. A matter that needs different access from the rest of a client’s work cannot simply sit one level down with tighter settings. It becomes its own shared folder, and those exceptions are identified before the tree is built.

  5. Shared folders count against storage

    A shared folder is added to each member’s account and normally counts towards their quota, and it syncs to their computer as a real folder. Sharing the whole client tree with every person can fill both. Shares are sized to teams, and the allowance needed per user is worked out from the document volumes.

More about moving into Sync.com

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Sync.com on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Local folders hold and how it is organised, then agree with you where each kind of record will sit in Sync.com. 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 Sync.com and checked against Local folders: 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 Local folders, a final pass over a weekend picks up what changed since the trial. Local folders are 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 Local folders 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 fromLocal folders
Moving toSync.com

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 Local folders holds

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

Structure, permissions and handover

Sync.com is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

A Sync set-up comes down to accounts and shares. A team plan gives an administrator control over users, two-factor authentication and password resets, which matters more than usual in a service the provider says it cannot see into. The shared folders are then created to match the firm’s teams and its restricted matters.

What is agreed and set up

  • Administrator account and a user for each staff member
  • Two-factor authentication enforced across the firm
  • Team shared folders with view or edit permission per person
  • Which matters live in Files and which in Vault
  • Rules for client links: passwords, expiry dates, upload rights
  • Desktop app installed, with a filing guide for new matters

Questions

Local folders to Sync.com: what firms ask

I am a sole practitioner and everything is on my laptop. Where do we start?

With a full copy of the laptop’s user folders taken to a second disk, before anything else. Then a list of your open matters, even handwritten. Folders are matched to that list, the rest is treated as closed files, and you check a sample in the new system before the laptop copy is retired.

Do you need to take our computers away?

No. It is the files that are needed, not the machines. Whether they are collected at each desk or remotely with the firm’s IT provider, and at what hours, is agreed in the analysis. A laptop needs to be switched on, signed in and on the office network or a reliable connection for as long as its copy takes.

What about personal files mixed in with work?

They stay where they are. Each person is shown the list of top-level folders found on their machine and marks the ones that are private. Those paths are excluded before any file is copied. Installed programs and system files are left out in any case.

Do documents from Local folders keep their folders and dates in Sync.com?

Sync.com stores documents. Files and folders within the path limit; some file types are skipped by the apps. 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.

What happens to records Sync.com has no place for?

On this route that is time entries and billing records. They are exported from Local folders in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

What has to be decided before Local folders data is loaded into Sync.com?

Emails, notes 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

Local folders and Sync.com are the names and marks of their owners, used here only to identify the two systems.

Moving from Local folders to Sync.com?

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

We reply within one business day.