Data migration route
ContactEase to Litify migration
ContactEase is a CRM and intake system, and Litify is a cloud case management system. Contacts and intake history move, and open enquiries become leads or cases in Litify.
ContactEaseCRM and intake- Contacts: Carried across
- Intake: Carried across
- 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
LitifyCloud- 2 carried
- 7 to confirm
What moves
What moves from ContactEase to Litify
Each row is a kind of record ContactEase holds, whether Litify has a place for it, and what is planned. On this route two kinds of record carry across 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. | Has a placeLoaded as parties and connected by roles. | Carried across |
| DocumentsFiles stored in or linked from the system | To be confirmed | Has a placeLoaded to the document component and attached to matters. | 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 partShown on the activity timeline. How old email is loaded is confirmed in the analysis. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeCalendar events on the matter. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a place | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeCustom fields are created before loading. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partTemplates are rebuilt in Litify’s document generation. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partBusiness development tracking and marketing lists. | Has a placeLoaded as intakes. | Carried across |
What the plans mean
- Carried across
- Litify has a place for this kind of record. It is loaded there and checked against ContactEase.
- 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
Intake history moves. The pipeline is rebuilt.
Intake data is the front end of a case. A lead in ContactEase carries the first conversation, the screening answers, the referrer and often a signed retainer. Many case management systems have an intake stage of their own, so a lead can land as a prospective case with that history attached. Where Litify has no such stage, open enquiries are loaded as contacts with their status in a note, and the firm decides which to open as cases.
Screening questions are the mapping work. Each intake form is a set of fields, and each field has to find a place on the case or be kept as a note. Referral sources are tidied into one list first, because they are usually typed by hand and reporting depends on them. Marketing automations, email sequences and web forms do not move as data. They are set up again in Litify or in the tool that feeds it.
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. ContactEase 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. Litify 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 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 Litify
Loading a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.
The design comes first
Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.
One party, many roles
Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.
Open enquiries load as intakes
Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.
Documents load after records
Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.
Validation rules reject bad rows
A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Litify on this route, which makes it repeatable: a load can be run again until it is right. The maker of Litify says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in ContactEase and checking each trial against ContactEase.
Analysis
We read what ContactEase holds and how it is organised, then agree with you where each kind of record will sit in Litify. 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 Litify 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 Litify. 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 Litify
Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.
A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.
Set-up decisions in Litify
- Define intake questionnaires and the rules for conversion
- Set case types, matter stages and page layouts
- Build matter plans that create tasks at each stage
- Design document folders and generation templates per case type
- Configure user roles and sharing for restricted matters
- Decide on timekeeping, billing and accounting integrations
Questions
ContactEase to Litify: 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 Litify?
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 Litify are exported into folders by client and matter.
Does everything in ContactEase have a place in Litify?
Most of it does on paper. Documents, emails, notes, calendar entries, tasks, custom fields and templates 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 Litify is kept as a readable archive, and you see which before the move.
What has to be decided before ContactEase data is loaded into Litify?
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 Litify
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 Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from ContactEase to Litify?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.