Data migration route
ContactEase to Server drives migration
ContactEase is a CRM and intake system, and Server drives are plain files on equipment the firm controls. What moves is the files, plus a readable export of everything else the old system holds.
ContactEaseCRM and intake- 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
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
Server drivesFiles- Contacts: Kept as a readable archive
- Intake: Kept as a readable archive
- 7 to confirm
- 2 archived
What moves
What moves from ContactEase to Server drives
Each row is a kind of record ContactEase holds, whether Server drives have a place for it, and what is planned. On this route two kinds have no place in Server drives and are archived and seven kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | HeldShared firm contacts with categories and mailing lists, used from Outlook. | No placeCan be kept only as an exported spreadsheet. | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | To be confirmed | Has a placeFiles in folders, named and dated during the load. | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | To be confirmedA built-in email campaign tool is included. | Has a place in partAs .msg or .eml files in each matter’s correspondence folder. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place in partAs a text or PDF file per matter, not as separate records. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | No place | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | No place | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | No place | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partPrecedents as Word files; merge fields tied to the old system stop working. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partBusiness development tracking and marketing lists. | No place | Kept as a readable archive |
What the plans mean
- 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
- Server drives has no place for it. It is exported in a format that opens without ContactEase 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
An export the firm can open without the system.
Server drives hold files, and most of what ContactEase 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 ContactEase, 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 Server drives is limited before the export is copied in.
How ContactEase 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. 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 ContactEase stays untouched until the copy in Server drives has been checked.
Where the data is now
Leaving ContactEase
ContactEase holds the firm’s shared view of who it knows: contacts, who at the firm knows each one, the lists they belong to and the business development activity logged against them. Moving off it is mostly a contact and mailing list project. The first step is confirming where the firm’s copy runs and how its data can be read, which differs between firms.
Firm contacts and Outlook contacts
Because the product works inside Outlook, the same person can appear in the firm’s shared contact list and in several lawyers’ own address books. The move works from the firm’s shared record. Lawyers keep their own Outlook contacts, and the analysis sets out how the two were connected in this firm’s set-up.
Who knows whom
SurePoint describes the product as a way to find who at the firm has the strongest relationship with a prospect. Most practice systems have one responsible lawyer per client and nowhere to list six others. Those connections are kept as a related-staff field, a note, or a separate list, depending on what the destination offers.
Mailing lists and categories
Marketing teams use the List Manager to maintain newsletters, alerts and invitation lists by practice area or industry. Lists are moved with their membership. Opt-outs are checked against the email tool the firm sends from, since that is usually where an unsubscribe is recorded.
Links to finance and marketing
SurePoint connects the product to its own financial management software, and it has links to HubSpot and Constant Contact. If the firm relies on any of those feeds, they stop when the CRM is replaced. Each feed is listed with what it carries, and a replacement is planned before cutover.
Where it is going
Arriving in Server drives
Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.
Agree the tree and the names
A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.
Budget the path length
Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.
Dates have to be set deliberately
A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.
Emails become message files
Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.
Keep an index beside the files
A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Server drives on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what ContactEase holds and how it is organised, then agree with you where each kind of record will sit in Server drives. 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 Server drives and checked against ContactEase: 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 ContactEase, a final pass over a weekend picks up what changed since the trial. ContactEase 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 ContactEase 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 ContactEase holds
What is in it, how its records link, and where each piece would sit in Server drives. 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
Server drives are 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 server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.
What is agreed and set up
- Share and top-level folders for clients, precedents and administration
- Security groups and folder permissions, with restricted matters separate
- Drive letter mapped for every user at sign-in
- Backup schedule and shadow copies for earlier versions
- Written naming rule for client, matter and document names
- Read-only area for closed matters and archived system exports
Questions
ContactEase to Server drives: what firms ask
Is ContactEase the same product as SurePoint CRM?
Yes. Cole Valley Software made ContactEase, and SurePoint Technologies acquired the company in 2022. SurePoint’s site now uses both names for the product. A firm that bought it years ago under the ContactEase name and a firm that licensed SurePoint CRM recently are moving the same kind of data.
Can our contacts go into a practice management system instead of another CRM?
The contacts can, with their addresses, categories and firm relationships. What a practice system rarely has is a place for list management and business development tracking. The analysis shows which fields have a home in the destination, which become notes, and whether a separate marketing tool should hold the lists.
Do documents from ContactEase keep their folders and dates in Server drives?
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 ContactEase before the plan is fixed. Documents that have no place in Server drives are exported into folders by client and matter.
What happens to records Server drives have no place for?
On this route that is contacts and intake records. They are exported from ContactEase 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 ContactEase data is loaded into Server drives?
Documents, emails, notes, calendar entries, tasks, custom fields and templates 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 ContactEase and into Server drives
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.
ContactEase and Server drives are the names and marks of their owners, used here only to identify the two systems.
Moving from ContactEase to Server drives?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.