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

Data migration route

BlueDot data to Microsoft SQL Server

BlueDot is a cloud case management system for immigration 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 BlueDot holds and keeps it readable and open to queries.

FromBlueDotCloud
  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
ToMicrosoft SQL ServerServer
  • 8 carried
  • 4 mapped
  • 1 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from BlueDot to Microsoft SQL Server

Each row is a kind of record BlueDot 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 one kind is confirmed in the analysis.

Records in BlueDot and their place in Microsoft SQL Server
RecordIn BlueDotIn Microsoft SQL ServerWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldImmigration cases linked to contacts and employers.Has a placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeldForeign nationals with biographic and history records, and employers.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldUploaded documents are stored encrypted; signed agreements save to the client file.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 partWith Office 365, emails to or copying a contact show in an Email Integration tab.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 and reminders on contacts, including speech-to-text notes.Has a placeRows of text linked to matters and contacts.Exported in full
CalendarAppointments, court dates and deadlinesHeldCalendar with two-way sync to Outlook 365 or Google Calendar.Has a placeRows of appointments and key dates; nothing displays them as a calendar.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeld in partReminders are kept with notes.Has a placeRows with assignee, due date and status.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeld in partTimesheets are listed among its advanced features.Has a placeTime and expense rows with rates and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeldInvoices, client balances, payment plans and online payment through PaySimple.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
Custom fieldsFields and record types the firm added itselfHeld in partQuestionnaires are fully customisable.Has a placeAs added columns, or a table of field names and values.Exported with mapping
TemplatesPrecedents, document templates and automationHeldUSCIS forms filled from questionnaire data, plus document assembly.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partClient questionnaires gather biographic and case data.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 BlueDot.
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 BlueDot 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 BlueDot 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.

BlueDot 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 BlueDot will release depends on its export tools, and that is confirmed in the analysis.

Where the data is now

BlueDot holds far more about a person than a general practice system expects: alien numbers, prior names, marriages, every address and employer. Most of that exists to fill immigration forms. Moving to a general system means deciding which of it becomes a field, which becomes a note, and which stays behind in an export the firm keeps. Another immigration system keeps more, but only field by field.

  1. The contact is the anchor

    Everything links back to a contact record for the foreign national, with separate history tables for addresses, marriages, employment, education and travel. A general system has one address and one employer per contact. The histories are either flattened into notes or loaded to custom fields, and the firm sees the mapping before the move.

  2. Employers and beneficiaries

    Business immigration cases join an employer to the people it sponsors. Employers are their own record type here, linked to contacts by an employer ID. In the destination the employer is normally the client and the foreign national a related party, so the relationship is rebuilt in that direction and checked on a sample of cases.

  3. Questionnaire answers

    Clients complete customisable questionnaires and their answers populate the forms. The answers are data, not documents, and each firm’s questionnaires differ. Every question in use is listed in the analysis, with whether the destination has a field for it. A PDF of each completed form can also be saved to the case in the new system.

  4. Filing fees and payments

    Billing is tied to PaySimple for client payments and payment plans, and to CorPay for virtual cards that pay USCIS filing fees, with each card linked to its case. Scheduled payments still to run are listed before cutover so none is taken twice or missed after the switch.

  5. Sensitive identifiers

    Contact records carry social security numbers, alien numbers and dates and places of birth. Who may see an extract of them is for the firm to decide before one is made, and the mapping records which of these fields the destination has a restricted place for and which the firm would prefer it did not hold at all.

More about moving off BlueDot

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

BlueDot to Microsoft SQL Server: what firms ask

Will our clients’ full immigration history come across?

It depends on the destination. Another immigration system will have places for prior addresses, employers and travel. A general practice system will not, and that history is carried as a structured note or an attached export on the contact. Nothing is dropped without the firm seeing the list first.

What happens to forms we have already filed?

Filed forms and the receipts or notices uploaded to a case are documents and move as documents, matched to the same case. The data that generated them moves separately as fields. Both are checked together on sample cases so the record in the new system agrees with what was lodged.

We sync BlueDot to QuickBooks. What changes?

BlueDot sends contacts, employers, invoices, payments and refunds to QuickBooks. After the move the new system has to take over that posting, or the firm enters it another way. The switch date is agreed with whoever keeps the books so that no invoice reaches QuickBooks from both systems.

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

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

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

Most of it does on paper. Trust ledgers 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 BlueDot 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 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

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

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