Data migration route
Claris FileMaker Pro to SharePoint migration
Claris FileMaker Pro is a desktop database, and SharePoint is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.
Claris FileMaker ProDesktop- Documents: Carried across
- Custom fields: Carried with mapping
- Matters: Confirmed in the analysis
- Contacts: Confirmed in the analysis
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Calendar: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Time and expenses: Confirmed in the analysis
- Billing: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
SharePointCloud- 1 carried
- 1 mapped
- 12 to confirm
What moves
What moves from Claris FileMaker Pro to SharePoint
Each row is a kind of record Claris FileMaker Pro holds, whether SharePoint 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.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | To be confirmedDepends entirely on what the firm built. | Has a place in partAs a site, library, folder or list row the firm designs; no built-in matter record. | Confirmed in the analysis |
| ContactsClients, other parties and referrers | To be confirmedMost firm-built systems start with a client table, but it is confirmed per system. | Has a place in partOnly as rows in a list built for the purpose. | Confirmed in the analysis |
| DocumentsFiles stored in or linked from the system | Held in partContainer fields can hold files, embedded, stored externally or by reference. | Has a placeFiles in libraries, with columns and versions. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partAs .msg or .eml files, with columns for sender and date if set up. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place in partAs documents, or as rows in a notes list if one is built. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a place in partPossible as a list; usually left in Outlook. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a place in partPossible as a list; no legal workflow built in. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | To be confirmed | No place | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | To be confirmed | No place | Confirmed in the analysis |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | No place | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | No place | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldEvery table and field was defined by the firm or its developer. | Has a placeColumns and content types on libraries and lists. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | To be confirmedLetters may be produced from layouts with merge fields; confirmed per system. | Has a place in partPrecedents as files; templates can be offered from a library. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | No place | Confirmed in the analysis |
What the plans mean
- Carried across
- SharePoint has a place for this kind of record. It is loaded there and checked against Claris FileMaker Pro.
- Carried with mapping
- SharePoint 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
An export the firm can open without the system.
SharePoint holds files, and most of what Claris FileMaker Pro holds is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used Claris FileMaker Pro, by client or by year, with a short index file saying what is where.
Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in SharePoint is limited before the export is copied in.
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. SharePoint 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
Leaving Claris FileMaker Pro
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in SharePoint
SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.
Site, library or folder per matter
A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.
Columns are built before content
If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.
The 400 character path
SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.
Large libraries and the view threshold
A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.
Security by library, not by file
Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in SharePoint on this route, which makes it repeatable: a load can be run again until it is right.
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 SharePoint. Anything with no place there stays behind or is archived, and you see which before the move.
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.
Trial load
A trial is loaded into SharePoint 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.
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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Claris FileMaker Pro holds
What is in it, how its records link, and where each piece would sit in SharePoint. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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
SharePoint 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.
Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.
What is agreed and set up
- Site and library structure for clients and matters
- Columns and content types for matter number and document type
- Permission groups, with restricted matters in their own libraries
- A repeatable way to create each new matter’s workspace
- Version history limits and retention labels for closed matters
- Views, indexed columns and search tested on loaded data
Questions
Claris FileMaker Pro to SharePoint: 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 SharePoint?
SharePoint stores documents. Files in libraries, with columns and versions. 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 SharePoint?
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 SharePoint 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 SharePoint?
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.
Other routes
Other routes from Claris FileMaker Pro and into SharePoint
Other destinations from Claris FileMaker Pro
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Claris FileMaker Pro and SharePoint are the names and marks of their owners, used here only to identify the two systems.
Moving from Claris FileMaker Pro to SharePoint?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.