Data migration route
filePro Plus data to Microsoft SQL Server
filePro Plus and Microsoft SQL Server are each a database on a server the firm runs. The move is technical: tables, column types and keys, checked row for row.
filePro PlusServer- Custom fields: Exported with mapping
- Matters: Confirmed in the analysis
- Contacts: Confirmed in the analysis
- Documents: 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
Microsoft SQL ServerServer- 1 mapped
- 13 to confirm
What moves
What moves from filePro Plus to Microsoft SQL Server
Each row is a kind of record filePro Plus holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route one kind needs mapping and thirteen kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | To be confirmedDepends on the application written for the firm. | Has a placeA table of matters linked to clients, parties and fee earners. | Confirmed in the analysis |
| ContactsClients, other parties and referrers | To be confirmed | Has a placePeople and companies, with their roles on each matter. | Confirmed in the analysis |
| DocumentsFiles stored in or linked from the system | To be confirmedConfirmed per application; a character-based system may hold none. | Has a place in partAs files in folders with an index table; storing files in the database is possible. | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partAs message files with an index table, or as rows of header fields. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeRows of text linked to matters and contacts. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeRows of appointments and key dates; nothing displays them as a calendar. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a placeRows with assignee, due date and status. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | To be confirmed | Has a placeTime and expense rows with rates and billed status. | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | To be confirmed | Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files. | Confirmed in the analysis |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a placeTransactions and balances for look-up; it is not a trust accounting system. | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | Has a placeGeneral ledger journals and balances, where the source held them. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldEvery file, field and screen was defined by the application’s developer. | Has a placeAs added columns, or a table of field names and values. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | To be confirmedOutput formats produce letters and forms; whether they are worth moving is per system. | Has a place in partPrecedent files can be stored; automation does not run here. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placeEnquiry rows, where the source recorded them. | Confirmed in the analysis |
What the plans mean
- Exported with mapping
- Microsoft SQL Server 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
Database to database, structure first.
Moving from filePro Plus to Microsoft SQL Server is the most mechanical route there is, and the easiest to check. Each table is recreated with matching columns, the rows are copied, and the counts are compared. The care goes into types. Dates, currency and long text are stored differently from one database to another, and a careless conversion cuts notes short or shifts a date by a day. Every column’s type is mapped on purpose and tested on real rows.
A home-built database usually has screens, reports and scripts on top of its tables, and those do not move with the data. If people still work in filePro Plus day to day, the firm needs to know what will replace the screens before the tables are moved. If the aim is an archive or a reporting copy, the tables are enough, and they are delivered with a written description of what each one holds and how they join.
Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in filePro Plus stays untouched until the copy in Microsoft SQL Server has been checked.
Where the data is now
Leaving filePro Plus
A filePro application has often been in service for decades, and one person in the office knows its menus by heart. Moving off it means recovering a description of the data from the application itself and from whoever still supports it, then checking the extracted figures against reports the old system prints.
Find who wrote the application
The firm’s supplier is often a small developer or reseller, not fP Technologies. Where they are still trading, their knowledge of the file layouts saves a good deal of time. If not, the analysis establishes whether the definitions can be read from the application’s own design screens. The firm is asked early for any contract, manual or contact name it still has.
Each file has its own layout
A filePro application is a collection of files, each with a defined list of fields, lengths and edit types, up to 999 fields in a record. There is no single schema document unless the developer wrote one. The layouts are captured file by file and turned into a data dictionary the firm can read.
Logic sits in processing tables
Balances, ageing and totals are often worked out by processing code when a screen opens or a report runs, and are not stored. Links between files are also expressed there as lookups. The code is read to find them, and calculated figures are taken from printed reports as control totals.
Fixed-length fields
Fields are fixed in length, so names and addresses may be cut short or split across lines in ways the developer chose. Dates and money follow the edit rules set for each field. Every field type is converted by a stated rule, and a sample of converted records is read against the old screens.
The machine it runs on
Some installations run on a Unix or Linux server reached through terminal software, which the firm’s current IT provider may never have managed. The analysis records where the application and data directories are, and the firm’s IT provider is asked whether the server can stay powered until the fall-back period ends.
Where it is going
Arriving in Microsoft SQL Server
There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.
Restored copy or rebuilt schema
Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.
No screens come with it
A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.
Documents sit beside the database
Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.
The edition follows the size
A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.
Backups and a test restore
An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.
How NewLaw runs it
Four steps, in this order.
This route produces an archive, not a working system, so the steps are about completeness and proof.
Analysis
We read what filePro Plus holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything filePro Plus holds is in scope unless you take it out.
Clean-up, if you want it
An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.
Trial export
The data is written to Microsoft SQL Server as a trial and checked against filePro Plus: record counts, totals where filePro Plus holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in filePro Plus, the export is run a final time and checked again. There is nothing to go live. filePro Plus is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.
Fixed price, agreed after the analysis. How NewLaw moves legal data
Start
Start this migration
Tell us what is in filePro Plus 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 filePro Plus holds
What is in it, how its records link, and where each piece would sit in Microsoft SQL Server. 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
Microsoft SQL Server is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.
Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.
What is agreed and set up
- Server, instance and edition agreed with the IT provider
- Read-only logins and roles for named staff
- Views for matter, ledger, time and document look-ups
- Backup schedule and who tests a restore
- Plain names and descriptions for tables and columns
- Excel or Power BI connected for reporting
Questions
filePro Plus to Microsoft SQL Server: what firms ask
Nobody supports our filePro system any more. Is the data recoverable?
Often, as long as the system still starts and someone can sign in. The data is on the server in the application’s files. What is confirmed in the analysis is whether the field definitions can be read from the application, and how much of the meaning can be recovered: which codes mean what, and which files are still in use.
How do we know nothing was lost in the conversion?
By comparing against the old system’s own reports. Before extraction the firm prints the reports it trusts: client list, open files, debtors, trust balances if the system holds them. After each trial load the same totals are produced from the new system. Differences are traced record by record until they are explained.
Does the old system hold our documents as well?
That depends on the application. Many character-based systems hold only data, with letters produced by merging into a word processor and saved on a server drive. If so, the documents are a separate source to be matched to the client and file numbers that come out of filePro. The analysis checks both.
Does the copy in Microsoft SQL Server hold documents from filePro Plus?
That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in filePro Plus before the plan is fixed.
Does everything in filePro Plus have a place in Microsoft SQL Server?
Most of it does on paper. Matters, contacts, documents, 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 Microsoft SQL Server is kept as a readable archive, and you see which before the move.
What has to be decided before filePro Plus is written out to Microsoft SQL Server?
Custom fields are exported with mapping, so each mapping is agreed with you first. Matters, contacts, documents, 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 who may open the archive and how long it is kept.
Other routes
Other routes from filePro Plus and into Microsoft SQL Server
Other destinations from filePro Plus
Other systems that move into Microsoft SQL Server
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.
filePro Plus and Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.
Moving from filePro Plus to Microsoft SQL Server?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.