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

Data migration route

Ciprocity data to Microsoft SQL Server

Ciprocity is a cloud case management system for legal aid work, 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 Ciprocity holds and keeps it readable and open to queries.

FromCiprocityCloud
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Notes: Exported in full
  4. Calendar: Exported in full
  5. Tasks: Exported in full
  6. Time and expenses: Exported in full
  7. Billing: Exported in full
  8. Intake: Exported in full
  9. Documents: Exported with mapping
  10. Emails: Exported with mapping
  11. Custom fields: Exported with mapping
  12. Templates: Exported with mapping
  13. Trust money: Confirmed in the analysis
  14. Firm accounts: Confirmed in the analysis
ToMicrosoft SQL ServerServer
  • 8 carried
  • 4 mapped
  • 2 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Ciprocity to Microsoft SQL Server

Each row is a kind of record Ciprocity holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route eight kinds of record carry across, four kinds need mapping and two kinds are confirmed in the analysis.

Records in Ciprocity and their place in Microsoft SQL Server
RecordIn CiprocityIn Microsoft SQL ServerWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases with problem codes, funding codes, assignments, closing codes and outcomes.Has a placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeldOne contact can appear on many cases in different roles; aliases are kept.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldA documents browser on each case, with OCR run on scanned uploads.Has a place in partAs files in folders with an index table; storing files in the database is possible.Exported with mapping
EmailsEmails saved to matters or to the storeHeld in partInbound email from staff accounts threads into the case; SMS messages are kept too.Has a place in partAs message files with an index table, or as rows of header fields.Exported with mapping
NotesFile notes, matter notes and contact notesHeldNotes are one kind of activity on the case.Has a placeRows of text linked to matters and contacts.Exported in full
CalendarAppointments, court dates and deadlinesHeldAppointments and ticklers on a shared calendar, with iCal and Office 365 sync.Has a placeRows of appointments and key dates; nothing displays them as a calendar.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldTicklers, and workflow rules that create them.Has a placeRows with assignee, due date and status.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldTime slips with activity type and funding source; optional supervisor approval.Has a placeTime and expense rows with rates and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeld in partNo client invoicing described; a grants manager keeps funder ledgers.Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a placeTransactions and balances for look-up; it is not a trust accounting system.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedHas a placeGeneral ledger journals and balances, where the source held them.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom fields and case tabs built by the program’s administrator.Has a placeAs added columns, or a table of field names and values.Exported with mapping
TemplatesPrecedents, document templates and automationHeldDocument assembly from .docx and RTF templates, form letters and docassemble.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldPrescreen, eligibility against poverty guidelines, duplicate and conflict checks.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 Ciprocity.
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

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

Writing Ciprocity 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 Ciprocity 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.

Ciprocity is hosted by its maker and Microsoft SQL Server sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What Ciprocity will release depends on its export tools, and that is confirmed in the analysis.

Where the data is now

Ciprocity gives each program its own instance and database, so the data to be moved belongs to one customer and nobody else’s is mixed in. The record design is specific to legal aid. People are contacts with roles on cases, work is a single stream of activities, and nearly everything is coded for a funder. A destination outside legal aid needs most of that translated.

  1. Roles belong to the case

    A contact holds the name, phone and address. Whether that person is the client, the opposing party or opposing counsel is recorded on the case, and one contact can hold different roles on different cases. Systems that file a contact as a client or as an other party need a rule for people who have been both.

  2. One stream of activities

    Notes, time slips, ticklers and appointments are all activities and share one history on the case. A destination system will split them into file notes, time entries, tasks and calendar events. Each activity type is mapped separately, and the trial load is checked by counting each type per case, not just the total.

  3. Closed means a date

    A case counts as closed when Date Closed is filled in, and closing also records a closing code and an outcome. Changing the status alone does not close it. Cases with a closed-looking status and no date are found in the analysis and put right, or they will arrive in the new system as open work.

  4. Three assignment slots

    Each case has a Primary Counsel, a co-counsel and a third assignee that is labelled Case Manager unless the program renamed it. Pro bono attorneys and referral recipients can also be recorded. A destination with one responsible lawyer per matter needs somewhere for the others, usually as related staff or a custom field.

  5. Locked and approved time

    Older time periods are locked so that months already reported to funders stay closed, and where approval is used, approved entries cannot be edited in the ordinary way. That state is part of the record. Time is loaded with its funding source and its approval status so a past grant report can be matched to the hours behind it.

More about moving off Ciprocity

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 Ciprocity holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything Ciprocity 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 Ciprocity: record counts, totals where Ciprocity 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 Ciprocity, the export is run a final time and checked again. There is nothing to go live. Ciprocity 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 Ciprocity 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 fromCiprocity
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 Ciprocity 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

Ciprocity to Microsoft SQL Server: what firms ask

Our contacts appear on dozens of cases. Will they be duplicated?

They should arrive once each. A Ciprocity contact is a single record linked to every case it has a role on, so the load creates the contact first and then the links. Duplicates that already exist are a separate matter. A merge pass before extraction is worthwhile for those.

Can ethical walls be carried across?

The walls themselves are a security setting in Ciprocity and cannot be copied into another product. The list of who is walled off from which case can be. It is extracted with the cases and used to set restrictions in the new system before any user logs in, then tested with an account that should be blocked.

What about the HUD, VAWA and immigration modules?

These are optional modules with their own fields and reports, switched on per program. Their data sits on the case and is moved as fields. The reporting they produce, such as HUD 9902 submissions, is a function of the software. If the destination cannot produce it, that reporting needs another home before cutover.

Does the copy in Microsoft SQL Server hold trust ledgers from Ciprocity?

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 Ciprocity before the plan is fixed.

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

Most of it does on paper. Trust ledgers and the firm’s accounts 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 Ciprocity is written out to Microsoft SQL Server?

Documents, emails, custom fields and templates are exported with mapping, so each mapping is agreed with you first. Trust ledgers and the firm’s accounts 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

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

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