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

Data migration route

Laserfiche to Sync.com migration

Laserfiche is a server-based document management system, and Sync.com is cloud file storage. Storage only has folders, so the move decides what of each document’s profile is kept in names and what in an index.

FromLaserficheServer
  1. Documents: Carried across
  2. Emails: Carried with mapping
  3. Notes: Carried with mapping
  4. Tasks: Confirmed in the analysis
  5. Templates: Confirmed in the analysis
  6. Intake: Confirmed in the analysis
ToSync.comCloud
  1. Custom fields: Kept as a readable archive
Readable archiveNo place in Sync.com
  • 1 carried
  • 2 mapped
  • 3 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Laserfiche to Sync.com

Each row is a kind of record Laserfiche holds, whether Sync.com has a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping, one kind has no place in Sync.com and is archived and three kinds are confirmed in the analysis.

Records in Laserfiche and their place in Sync.com
RecordIn LaserficheIn Sync.comWhat is planned
DocumentsFiles stored in or linked from the systemHeldEntries in repository folders: scanned pages with text, or electronic files.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 partImported emails use an Email template that holds the message details.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 partAnnotations on documents are stored in the repository database.Has a place in partOnly as a document written out to the matter’s folder.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleTo be confirmedWorkflow and forms are part of the platform; use varies by installation.No placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldFields and templates are defined in repository administration.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partPrecedents load as ordinary files.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeConfirmed in the analysis

What the plans mean

Carried across
Sync.com has a place for this kind of record. It is loaded there and checked against Laserfiche.
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.
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.
Kept as a readable archive
Sync.com has no place for it. It is exported in a format that opens without Laserfiche 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

Profiles flatten into folders and an index.

A document management system knows things about a file that a folder cannot hold: its profile, its versions, who may open it. Moving from Laserfiche to Sync.com flattens that. Client and matter become folder levels. Document type may become a subfolder. Versions become separate files with a suffix, or only the latest is kept. Each of these is a choice the firm makes before the export, and the result is tested on a sample of real matters.

What the folders cannot carry goes into an index: a spreadsheet listing every exported file with its document number, author, dates, type and original location. With it, a document cited by number in an old email can still be found. Access restrictions do not transfer by themselves. Restricted workspaces are exported to separate folders, and permissions are set on those in Sync.com before anyone else is given access.

Laserfiche 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. Sync.com 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

Many Laserfiche documents are not files in the usual sense. An imaged document is a set of scanned pages with recognised text stored beside them, held in a volume and described in the database. Getting it out means generating a PDF from those pages. Electronic documents come out in their original format. The export has to handle both kinds and carry the template fields with them.

  1. Imaged and electronic documents

    An imaged document has page images and text but no original file, and opens in Laserfiche’s own viewer. An electronic document is tied to a file such as a Word document. On export, imaged documents are rendered to PDF with their text, and that conversion is tested for page counts and for whether the result can be searched.

  2. Templates carry client and matter

    Fields are grouped into templates. Where a firm built a client-file template with client number, matter number and document type, those fields drive the mapping. Documents with no template, or with the General template only, are filed from their folder path instead, and the two groups are counted separately.

  3. Volumes and the database

    In a self-hosted repository the content is in volumes, which can be spread over several drives or servers, and everything that says what it is sits in the database. Extraction is done through Laserfiche, not by copying volume folders, because a volume on its own does not say which pages make up which document.

  4. Retention rules

    A repository used for records management has retention rules applied to its folders. A legal document system may record when a matter closed but rarely has the same machinery. The rules in force are written down before cutover, so the firm’s retention obligations are not lost along with the software.

  5. Rights on fields and templates

    Access can be set on folders and documents, and also on individual fields and templates, so a user may see a document but not one sensitive field on it. Field-level restrictions rarely have an equivalent elsewhere. Sensitive fields are dropped, loaded to a restricted note, or the documents themselves are restricted.

More about moving off Laserfiche

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 Laserfiche holds 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 Laserfiche: 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 Laserfiche, a final pass over a weekend picks up what changed since the trial. Laserfiche 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 Laserfiche 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 fromLaserfiche
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 Laserfiche 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

Laserfiche to Sync.com: what firms ask

Most of our Laserfiche is scanned paper. Does it stay searchable?

It can. Laserfiche stores the recognised text for each scanned page, and an export to PDF can include it as a text layer. Whether the new system searches that layer or runs its own recognition differs by product. A sample is loaded and searched during the trial, before the full volume is converted.

Can folder structure and template fields both be kept?

Usually one becomes the primary key and the other is kept as supporting data. If the destination files by client and matter, those fields decide where a document goes, and the old folder path is written into a description or sub-folders. Fields with no equivalent are listed for the firm to keep as notes or drop.

Do documents from Laserfiche 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 custom fields. They are exported from Laserfiche 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 Laserfiche data is loaded into Sync.com?

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

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

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