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

Data migration route

Alfresco to Google Drive migration

Alfresco is a document management system, and Google Drive 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.

FromAlfrescoDocument management
  1. Documents: Carried across
  2. Emails: Confirmed in the analysis
  3. Notes: Confirmed in the analysis
  4. Calendar: Confirmed in the analysis
  5. Tasks: Confirmed in the analysis
  6. Templates: Confirmed in the analysis
ToGoogle DriveCloud
  1. Custom fields: Kept as a readable archive
Readable archiveNo place in Google Drive
  • 1 carried
  • 5 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Alfresco to Google Drive

Each row is a kind of record Alfresco holds, whether Google Drive has a place for it, and what is planned. On this route one kind of record carries across, one kind has no place in Google Drive and is archived and five kinds are confirmed in the analysis.

Records in Alfresco and their place in Google Drive
RecordIn AlfrescoIn Google DriveWhat is planned
DocumentsFiles stored in or linked from the systemHeldFiles in repository folders and site document libraries, with typed properties.Has a placeAny file type, stored as uploaded or converted to Google formats.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedDepends on the modules and integrations installed.Has a place in partAs .eml or .msg files in the matter folder; not as Gmail messages.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs a Doc or Word file in the matter’s folder.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedNo placeCalendar entries belong in Google Calendar.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedWorkflow tasks exist where the process services are in use.No placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom types, aspects and properties defined in a content model.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partPrecedents load as files; the load does not rebuild Word automation in Docs.Confirmed in the analysis

What the plans mean

Carried across
Google Drive has a place for this kind of record. It is loaded there and checked against Alfresco.
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
Google Drive has no place for it. It is exported in a format that opens without Alfresco 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 Alfresco to Google Drive 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 Google Drive before anyone else is given access.

How Alfresco is run at the firm is settled at the start of the analysis, because its maker’s own material does not settle it. The usual arrangement is assumed here. Alfresco 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. Google Drive 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

No two Alfresco installations are alike, because the content model is written for each customer. A move off it begins by reading that model: which custom types and aspects exist, what properties they carry, and how the firm used sites and folders to stand for clients and matters. Only then can anyone say which properties are matter numbers and which are noise.

  1. Read the content model

    Document types, their properties and the aspects applied to them are defined in content models specific to the installation. A property might be called matterRef at one firm and caseNo at another. The model files and a sample of live documents are examined together to build the field list the mapping works from.

  2. Versioning is not always on

    Alfresco’s documentation notes that content created in the repository is not versioned by default: history is kept once versioning has been applied to the item. So some documents will have a full history and others a single state. The extraction records which is which instead of assuming every file has versions.

  3. Sites, libraries and plain folders

    Content can sit in a site’s document library or in ordinary repository folders outside any site. Firms often have both: sites created per client or project, and an older folder tree brought in from a file server. Each is walked separately, and an item filed in more than one place is counted once.

  4. Customisations hold business rules

    Folder rules, scripts and workflows are commonly added to file documents automatically, stamp metadata or route approvals. They are configuration, not data, and they do not move. The analysis lists the ones that still run, so the firm can decide which behaviours it needs the new system to reproduce.

  5. Community or supported edition

    Which edition and version is running affects how the repository is reached and what help is available with it. A self-hosted Community Edition is entirely in the firm’s hands. The edition, the version and any add-on modules installed are recorded at the start of the analysis.

More about moving off Alfresco

Where it is going

Putting a firm’s matter files into Google Drive means choosing shared drives over personal ones and then deciding how many shared drives there should be. That second decision is driven by Google’s limits and by who is allowed to see what, since access is granted mainly at the level of the whole shared drive.

  1. Shared drives, not My Drive

    Files loaded into a shared drive belong to the firm and remain when the person who loaded them leaves. Anything loaded into someone’s My Drive belongs to that person. Matter files therefore go to shared drives, and My Drive is left for personal working papers.

  2. One drive cannot hold everything

    Google caps a shared drive at 500,000 items, counting folders, shortcuts and anything in the trash, and at 100 levels of nested folders. A firm with twenty years of matters can pass the item cap in a single drive. The split is planned up front, commonly by practice group, or by open and closed matters.

  3. Membership is the main control

    Every member of a shared drive can see all of it unless a Manager restricts a particular folder. Matters that only certain people may open are simpler to protect in a shared drive of their own. The firm supplies the list of restricted matters and partners’ private folders before the drives are created.

  4. The daily upload limit

    Each user can upload 750 GB to Drive in 24 hours, and then has to wait. For a large document set that limit sets the shortest time the load can take. The total size is measured in the analysis, so the firm knows before the freeze whether its documents fit inside a weekend.

  5. Keep Office files as Office files

    Word and Excel files can be stored in Drive as they are or converted to Google formats. Unless the firm asks otherwise they are loaded unconverted, so court documents and automated precedents arrive as they left. The firm decides afterwards which templates are worth rebuilding as Google Docs.

More about moving into Google Drive

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

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

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

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

Google Drive 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 Drive set-up for a law firm is a small number of deliberate choices made in the Workspace Admin console and then left alone. Which shared drives exist, who manages each, whether staff may share outside the firm, and whether people work from the browser or from Drive for desktop. Staff also need to be shown where a new matter folder goes.

What is agreed and set up

  • Shared drives by practice group, with a naming pattern
  • Managers and member access levels for each shared drive
  • External sharing rules set in the Admin console
  • Drive for desktop on PCs that need Explorer access
  • A standard subfolder set copied into every new matter
  • Transfer of leavers’ My Drive files as a standing procedure

Questions

Alfresco to Google Drive: what firms ask

Alfresco is not a legal system. Can its documents still be loaded into one by matter?

Yes, if each document can be tied to a matter by something reliable: a property, the site it is in, or its folder path. The analysis tests that on the real data and reports how many documents fall outside the rule. Those are assigned by hand, loaded to a holding matter, or kept only in the old system.

Do metadata and versions come across?

Properties can be extracted for every item, and versions where versioning was applied. Where they land depends on the destination: a legal document system has a fixed set of profile fields plus some custom ones. Properties with no equivalent are written into a note or description, or left behind, and the firm sees the list first.

Do documents from Alfresco keep their folders and dates in Google Drive?

Google Drive stores documents. Any file type, stored as uploaded or converted to Google formats. 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 Google Drive has no place for?

On this route that is custom fields. They are exported from Alfresco 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 Alfresco data is loaded into Google Drive?

Emails, notes, calendar entries, tasks and templates 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

Alfresco and Google Drive are the names and marks of their owners, used here only to identify the two systems.

Moving from Alfresco to Google Drive?

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

We reply within one business day.