Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

ContactEase data to Microsoft SQL Server

ContactEase is a CRM and intake system, and Microsoft SQL Server is a database on a server the firm runs. This is not a move to a new working system: the route writes out what ContactEase holds and keeps it readable and open to queries.

FromContactEaseCRM and intake
  1. Contacts: Exported in full
  2. Intake: Exported in full
  3. Documents: Confirmed in the analysis
  4. Emails: Confirmed in the analysis
  5. Notes: Confirmed in the analysis
  6. Calendar: Confirmed in the analysis
  7. Tasks: Confirmed in the analysis
  8. Custom fields: Confirmed in the analysis
  9. Templates: Confirmed in the analysis
ToMicrosoft SQL ServerServer
  • 2 carried
  • 7 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from ContactEase to Microsoft SQL Server

Each row is a kind of record ContactEase holds, whether Microsoft SQL Server 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.

Records in ContactEase and their place in Microsoft SQL Server
RecordIn ContactEaseIn Microsoft SQL ServerWhat is planned
ContactsClients, other parties and referrersHeldShared firm contacts with categories and mailing lists, used from Outlook.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemTo be confirmedHas 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 storeTo be confirmedA built-in email campaign tool is included.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 notesTo be confirmedHas a placeRows of text linked to matters and contacts.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeRows of appointments and key dates; nothing displays them as a calendar.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeRows with assignee, due date and status.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeAs added columns, or a table of field names and values.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partPrecedent files can be stored; automation does not run here.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesHeld in partBusiness development tracking and marketing lists.Has a placeEnquiry rows, where the source recorded them.Exported in full

What the plans mean

Exported in full
Microsoft SQL Server 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

Not a new system. A complete copy the firm can query.

Writing ContactEase out to Microsoft SQL Server is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.

What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in ContactEase as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.

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 Microsoft SQL Server has been checked.

Where the data is now

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

More about moving off ContactEase

Where it is going

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving into Microsoft SQL Server

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.

  1. Analysis

    We read what ContactEase holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything ContactEase holds is in scope unless you take it out.

  2. 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.

  3. Trial export

    The data is written to Microsoft SQL Server as a trial and checked against ContactEase: record counts, totals where ContactEase holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in ContactEase, the export is run a final time and checked again. There is nothing to go live. ContactEase 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 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

Step 1 of 5: Start with the route

Moving fromContactEase
Moving toMicrosoft SQL Server

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what ContactEase 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.

  3. 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

ContactEase to Microsoft SQL Server: 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.

Does the copy in Microsoft SQL Server hold documents from ContactEase?

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.

Does everything in ContactEase have a place in Microsoft SQL Server?

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 Microsoft SQL Server is kept as a readable archive, and you see which before the move.

What has to be decided before ContactEase is written out to Microsoft SQL Server?

Documents, emails, notes, calendar entries, tasks, custom fields and templates are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.

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.

How we do itDiscovery to rollout, step by step

ContactEase and Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.

Moving from ContactEase 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.