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

Data migration route

Claris FileMaker Pro to NetDocuments migration

Claris FileMaker Pro is a desktop database, and NetDocuments is a cloud document management system. Only files and their details have a place there, so this route carries the documents and archives the rest.

FromClaris FileMaker ProDesktop
  1. Documents: Carried across
  2. Custom fields: Carried with mapping
  3. Matters: Confirmed in the analysis
  4. Contacts: Confirmed in the analysis
  5. Emails: Confirmed in the analysis
  6. Notes: Confirmed in the analysis
  7. Calendar: Confirmed in the analysis
  8. Tasks: Confirmed in the analysis
  9. Time and expenses: Confirmed in the analysis
  10. Billing: Confirmed in the analysis
  11. Trust money: Confirmed in the analysis
  12. Firm accounts: Confirmed in the analysis
  13. Templates: Confirmed in the analysis
  14. Intake: Confirmed in the analysis
ToNetDocumentsCloud
  • 1 carried
  • 1 mapped
  • 12 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Claris FileMaker Pro to NetDocuments

Each row is a kind of record Claris FileMaker Pro holds, whether NetDocuments has a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping and twelve kinds are confirmed in the analysis.

Records in Claris FileMaker Pro and their place in NetDocuments
RecordIn Claris FileMaker ProIn NetDocumentsWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusTo be confirmedDepends entirely on what the firm built.Has a place in partAs a client and matter value with its workspace. Other matter details stay in practice management.Confirmed in the analysis
ContactsClients, other parties and referrersTo be confirmedMost firm-built systems start with a client table, but it is confirmed per system.No placeConfirmed in the analysis
DocumentsFiles stored in or linked from the systemHeld in partContainer fields can hold files, embedded, stored externally or by reference.Has a placeImported with profile values, folder, dates and access set per document.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeLoaded as email items profiled to the matter.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedNo placeFile notes are loaded as documents in the matter workspace.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedNo placeConfirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedTo be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledTo be confirmedNo placeConfirmed in the analysis
BillingInvoices, payments and debtor balancesTo be confirmedNo placeConfirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedNo placeConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedNo placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldEvery table and field was defined by the firm or its developer.Has a placeAs custom profile attributes, created in the repository before the load.Carried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedLetters may be produced from layouts with merge fields; confirmed per system.Has a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeConfirmed in the analysis

What the plans mean

Carried across
NetDocuments has a place for this kind of record. It is loaded there and checked against Claris FileMaker Pro.
Carried with mapping
NetDocuments 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

Only the documents have a place here.

NetDocuments is a document management system: it takes files and the details that describe them. Most of what Claris FileMaker Pro holds is not files. Entries, balances, settings and lists have no place in a document store, and the table above is short for that reason. What can move is any document Claris FileMaker Pro produced or stored: invoices as PDFs, signed agreements, attachments, exported reports. Each is filed under the client or matter it relates to.

The useful version of this job is often an archive. A firm retiring a system wants its records readable later without keeping the subscription or the old PC. The data is exported in open formats, spreadsheets and PDFs, and filed in NetDocuments in a workspace set aside for it, with access limited to the people who need it. That gives the firm one place to look, under the same retention rules as the rest of its documents.

Claris FileMaker Pro 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. NetDocuments 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

With a firm-built system there is no vendor manual describing the data, so the first job is to write one. The design is read out of the FileMaker files themselves, then walked through with the person who knows the system best. Only after that can anyone say what it holds, which parts are still used, and where each field will go.

  1. Read the design from the file

    FileMaker can produce a Database Design Report, or save a copy of the file as XML, setting out every table, field, relationship, layout and script. Either needs an account with full access privileges. That report is the starting document for the analysis, and it can turn up tables nobody remembers.

  2. Layouts are not tables

    Staff know the system by its screens. A single matter layout may draw on five related tables through portals and lookups. Exports run table by table, so each screen is traced back to the tables behind it and the key fields that join them are carried through, or the links are lost.

  3. Documents in container fields

    A container field can hold a document embedded in the database, stored in an external folder that FileMaker manages, or only as a reference to a file elsewhere. Each kind is extracted differently. References are tested, because a path recorded in 2012 may point to a server that no longer exists.

  4. Calculated and summary fields

    A matter balance or total hours shown on screen may be a calculation, not stored data. An export gives the result as it stood that day. The firm chooses between bringing the figure as a fixed number and bringing the underlying entries so the new system can work it out again.

  5. Free typing and private conventions

    Home-built systems rarely validate what is typed. The same court appears under six spellings, dates sit in text fields, and one field has been reused for something else since 2015. Clean-up therefore takes longer here than for a packaged product, and the firm sees the proposed standard values first.

More about moving off Claris FileMaker Pro

Where it is going

Loading into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.

  1. Lookup tables before documents

    Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.

  2. Workspaces come from the profile

    A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.

  3. Import files are unforgiving

    The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.

  4. Folder limits and depth

    A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.

  5. Security at the right level

    Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.

More about moving into NetDocuments

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

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

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 Claris FileMaker Pro holds

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

Loaded data is not yet a working system. This is what NewLaw sets up in NetDocuments, beyond the migration, so that people can work in it from the first day.

Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.

Set-up decisions in NetDocuments

  • Cabinet design: one for the firm, or several by purpose
  • Profile attributes, lookup tables and the client and matter hierarchy
  • Workspace layout with default folders, filters and saved searches
  • User groups, cabinet membership and security for restricted matters
  • A feed of new clients and matters from practice management
  • ndOffice, ndMail and Outlook filing on every desk, with training

Questions

Claris FileMaker Pro to NetDocuments: what firms ask

The person who built our system has gone. Can it still be moved?

Usually, provided someone holds a full access account for the files. With that, the design can be read without the developer. Without it, data can still be exported from whatever the firm’s own logins can see, but the scripts and hidden tables cannot be inspected, and the analysis takes longer and says so.

Our system does things no legal product does. What happens to those?

Each one is listed in the analysis and put in one of three groups: the new system does it differently, the new system can be configured to do it, or it will stop. The third group is the one to discuss with the partners early. A custom register can also be kept as an exported spreadsheet.

Can we keep FileMaker for reference afterwards?

Yes. The files can be left on the server, or a copy opened in FileMaker Pro on one PC, with accounts changed to read only so nothing new is entered. That is the fall-back record. It depends on keeping a working FileMaker licence and a machine that runs it, which the firm should note for later years.

Do documents from Claris FileMaker Pro keep their folders and dates in NetDocuments?

NetDocuments stores documents. Imported with profile values, folder, dates and access set per document. 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 Claris FileMaker Pro have a place in NetDocuments?

Most of it does on paper. Matters, contacts, emails, notes, calendar entries, tasks, time entries, billing records, trust ledgers, the firm’s accounts, templates and intake records 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 NetDocuments is kept as a readable archive, and you see which before the move.

What has to be decided before Claris FileMaker Pro data is loaded into NetDocuments?

Custom fields are carried with mapping, so each mapping is agreed with you first. Matters, contacts, emails, notes, calendar entries, tasks, time entries, billing records, trust ledgers, the firm’s accounts, 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

Claris FileMaker Pro and NetDocuments are the names and marks of their owners, used here only to identify the two systems.

Moving from Claris FileMaker Pro to NetDocuments?

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

We reply within one business day.