Data migration route
Elite 3E to SimpleLaw migration
Elite 3E is a server-based accounting and billing system, and SimpleLaw is a cloud practice management system. The financial records lead: balances and open items move, and the matters in SimpleLaw are built around them.
Elite 3EServer- Matters: Carried across
- Contacts: Carried across
- Time and expenses: Carried across
- Intake: Carried across
- Billing: Carried with mapping
- Trust money: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- 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
SimpleLawCloud- Firm accounts: Kept as a readable archive
- 4 carried
- 4 mapped
- 5 to confirm
- 1 archived
What moves
What moves from Elite 3E to SimpleLaw
Each row is a kind of record Elite 3E holds, whether SimpleLaw has a place for it, and what is planned. On this route four kinds of record carry across, four kinds need mapping, one kind has no place in SimpleLaw and is archived and five kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldClients and matters are the core of the financial record. | Has a place | Carried across |
| ContactsClients, other parties and referrers | Held in partClients, timekeepers and vendors as financial records. | Has a placeAs leads, clients or other contacts in the CRM. | Carried across |
| DocumentsFiles stored in or linked from the system | To be confirmed | Has a placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive. | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | To be confirmed | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a place | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a place | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime capture feeding work in progress on each matter. | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | HeldProformas, invoices, e-billing through eBillingHub, payments and collections. | Has a place in partInvoices are created in the product; loading invoice history is confirmed in the analysis. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | HeldTrust is one of the areas 3E Notify covers, with billing, payables and the ledger. | Has a place in partTrust balances are supported; history depth is confirmed in the analysis. | Carried with mapping |
| Firm accountsGeneral ledger, office account and payables | HeldMulti-entity, multi-currency general ledger, accounts payable and budgeting. | No placeGeneral ledger stays in QuickBooks or another accounting package. | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldElite’s own migration guide inventories each firm’s customisations. | Has a place | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partProforma and invoice templates. | Has a place in partTemplates are rebuilt using SimpleLaw’s own automation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partClient and matter intake, which Elite’s data tools standardise. | Has a placeLeads and intake forms. | Carried across |
What the plans mean
- Carried across
- SimpleLaw has a place for this kind of record. It is loaded there and checked against Elite 3E.
- Carried with mapping
- SimpleLaw 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
- SimpleLaw has no place for it. It is exported in a format that opens without Elite 3E 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
Time, bills and balances move. How much history is a decision.
Coming from an accounting or billing system, the records that count are balances: unbilled time, unpaid invoices, client funds, the ledger. A practice management system takes these as opening positions on a matter. So every client and job in Elite 3E needs a matter to land on, and the first piece of work is building that matter list, often from client and project codes that were never meant to be matter numbers.
How much history to bring is the main choice. Paid invoices from years ago can be loaded as records, kept as PDF copies on the matter, or left in a read-only copy of Elite 3E. Most firms bring open items and a period of history, and keep the rest as reports. Opening balances in SimpleLaw are agreed to the trial balance and aged debtors from Elite 3E as at the cutover date, and that load is rehearsed before it is done for real.
Elite 3E 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. SimpleLaw 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 Elite 3E
Firms on Elite are large, and so is the data: every time entry, proforma, invoice and ledger posting for the life of the firm, usually across more than one office or entity. Moving to a different system starts with which Elite product and version is in place, then with how much of that history has to be live in the new system on day one.
Which Elite it is
3E in Elite’s cloud, 3E on the firm’s own SQL Server and the older Enterprise system keep their data differently and are reached differently. An on-premises firm can copy its own database. A cloud firm works from what Elite’s service provides. The product, version and hosting are confirmed before anything is scoped.
Proformas and write-downs
Billing runs through proformas that partners edit before an invoice is posted, and the edits, write-downs and transfers are part of the record. Most destinations keep the final invoice only. The firm decides whether proforma history matters for reporting on realisation, and if so where it will be kept.
More than one entity
The 3E general ledger is built to consolidate several entities and currencies. A firm with offices in different countries may be one database with many sets of books. The new system’s structure for offices and currencies is settled first, since every matter and balance has to be assigned to one.
Customisations get an inventory
Elite’s own cloud migration program begins by listing every customisation a firm has in production, a sign of how much firm-specific configuration these systems carry. Custom fields, rules, reports and templates built in 3E are listed the same way here, and each is matched to something in the destination or dropped by decision.
E-billing rules and client guidelines
Firms that bill corporate clients electronically check invoices against client billing guidelines in Elite’s Validate and eBillingHub products before sending them. Those rules belong to the client relationship, not to the software. They are set up again in whatever the destination uses for e-billing, so invoices are not rejected in the first month.
Where it is going
Arriving in SimpleLaw
Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.
Lead, client or contact
A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.
Billing type on each matter
Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.
Storage chosen before loading
If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.
Custom fields named for templates
Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.
Portal access client by client
The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.
How NewLaw runs it
Four steps, in this order.
Trust money moves on this route, so the trust cutover gets a rehearsal of its own.
Analysis
We read what Elite 3E holds and how its records link, then agree with you, field by field, where each piece will sit in SimpleLaw. Anything with no place there comes across as a note or stays behind, and you see which before the move.
Clean-up
Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Elite 3E, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into SimpleLaw as a trial and checked against Elite 3E: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Elite 3E are frozen for an agreed window, the data is collected a final time and SimpleLaw goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. Elite 3E 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 Elite 3E 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 Elite 3E holds
What is in it, how its records link, and where each piece would sit in SimpleLaw. 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
Setting up SimpleLaw
Loaded data is not yet a working system. This is what NewLaw sets up in SimpleLaw, beyond the migration, so that people can work in it from the first day.
The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.
Set-up decisions in SimpleLaw
- Labels for documents, activities, expenses and contact IDs
- Custom fields and intake forms for each practice area
- Document templates and the attorney-client agreement
- Workflows for case types that follow a standard process
- User permission sets and client portal visibility
- QuickBooks connection and the online payment processor
Questions
Elite 3E to SimpleLaw: what firms ask
Does it matter whether we are on 3E or Enterprise?
It does. They are different systems with different databases, and 3E itself comes as a cloud service or an on-premises installation. The records are the same in kind: clients, matters, time, bills, trust and ledgers. How they are extracted and how the totals are checked is worked out for the product you have.
Can we bring all our financial history?
Rarely all of it as live transactions. Open matters, unbilled time, unpaid invoices, trust balances and opening ledger balances are the part that has to be live. Older detail is usually summarised, with the Elite database kept read only for look-ups. How far back the live detail goes is a decision for the finance team.
What about our matter numbers?
Client and matter numbers are read as they stand and carried into the new system wherever it allows the number to be set. Firms whose numbers join a client code to a matter code should check the destination’s field lengths early, which the field mapping in the analysis does.
Do trust balances in Elite 3E have a place in SimpleLaw?
In part. Trust balances are supported; history depth is confirmed in the analysis. The analysis sets out which trust records have a place in SimpleLaw and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.
What happens to records SimpleLaw has no place for?
On this route that is the firm’s accounts. They are exported from Elite 3E 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 Elite 3E data is loaded into SimpleLaw?
Billing records, trust ledgers, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Documents, emails, notes, calendar entries and tasks are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from Elite 3E and into SimpleLaw
Other destinations from Elite 3E
Other systems that move into SimpleLaw
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.
Elite 3E and SimpleLaw are the names and marks of their owners, used here only to identify the two systems.
Moving from Elite 3E to SimpleLaw?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.