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

Data migration route

BlueDot data to Full data export

BlueDot is a cloud case management system for immigration work, and Full data export is a store of data kept as files the firm holds. 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. Documents: Exported in full
  4. Notes: Exported in full
  5. Calendar: Exported in full
  6. Tasks: Exported in full
  7. Time and expenses: Exported in full
  8. Billing: Exported in full
  9. Emails: Exported with mapping
  10. Custom fields: Exported with mapping
  11. Templates: Exported with mapping
  12. Intake: Exported with mapping
  13. Trust money: Confirmed in the analysis
ToFull data exportFiles
  • 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 Full data export

Each row is a kind of record BlueDot holds, whether Full data export 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 Full data export
RecordIn BlueDotIn Full data exportWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldImmigration cases linked to contacts and employers.Has a placeA matters table keyed by the original matter number.Exported in full
ContactsClients, other parties and referrersHeldForeign nationals with biographic and history records, and employers.Has a placeA contacts table and a table of each contact’s role 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 placeFiles under their original names, in client and matter folders.Exported in full
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 partFiled emails as message files in the matter’s folder, if the source exposes them.Exported with mapping
NotesFile notes, matter notes and contact notesHeldNotes and reminders on contacts, including speech-to-text notes.Has a placeA notes table with matter, author and date for each note.Exported in full
CalendarAppointments, court dates and deadlinesHeldCalendar with two-way sync to Outlook 365 or Google Calendar.Has a placeA table of appointments and key dates; nothing shows it as a diary.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeld in partReminders are kept with notes.Has a placeA table of tasks 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 placeA time entries table with fee earner, matter, units, rate and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeldInvoices, client balances, payment plans and online payment through PaySimple.Has a placeInvoice, line and receipt tables; invoice PDFs can be kept beside them.Exported in full
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a placeA trust transactions table; ledger reports can be kept as PDF beside it.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeld in partQuestionnaires are fully customisable.Has a placeExtra columns under their original field names.Exported with mapping
TemplatesPrecedents, document templates and automationHeldUSCIS forms filled from questionnaire data, plus document assembly.Has a place in partTemplate files only; the merge fields in them will not run.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partClient questionnaires gather biographic and case data.Has a place in partAn enquiries table, where the source tracked leads.Exported with mapping

What the plans mean

Exported in full
Full data export has a place for this kind of record. It is loaded there and checked against BlueDot.
Exported with mapping
Full data export 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 Full data export 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 Full data export 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

A full export is judged by whether a stranger can use it. In five years the question will be something like: what was the trust balance on this matter the day it closed, and where is the signed agreement. The export is planned backwards from questions of that kind, and it is checked against the live system while the live system can still be opened.

  1. Tables that still join up

    Each kind of record becomes its own table: matters, contacts, time entries, invoices, trust transactions. The identifiers that link them are kept in every table, so a time entry can still be traced to its matter and its fee earner. An export that keeps the rows and drops the keys cannot be rejoined later.

  2. Documents with an index

    Documents are written to folders by client and matter under their original names. On their own they can be found only by name. An index listing each file with its matter number, title, author, dates and path is what lets someone find the right version of a lease among forty thousand files without the old system’s search. What the index records is settled in the analysis.

  3. Reports a person can read

    Raw tables do not satisfy an auditor or a former client. The firm decides which reports are also printed to PDF from the old system as at the final date: trust ledgers, matter ledgers, debtor lists and issued invoices are the usual candidates. They cannot be regenerated once the licence ends.

  4. What an export does not keep

    Screens, workflows, document automation, saved searches and user permissions belong to the software and stay with it. Figures the system calculated on the fly, such as a matter’s unbilled total, exist in an export only if they were captured as a report. The firm is told which of these are being let go.

  5. Checked while the source is open

    Record counts and financial totals in the export are reconciled to the live system: number of matters, sum of trust balances, total debtors, document count per matter on a sample. This is done before the subscription lapses or the server is turned off, because afterwards there is nothing left to compare against.

More about moving into Full data export

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 Full data export 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 Full data export 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 toFull data export

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 Full data export. 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

Full data export 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.

With no product to configure, the set-up is custody, and the decisions are the firm’s. Someone there owns the export, knows where it is kept and can open it. Access needs restricting, because it contains every client’s affairs in one place with none of the old system’s security. The firm sets a destruction date from its retention obligations and decides how the next custodian will learn to use it.

What is agreed and set up

  • Folder layout for tables, documents and reports
  • What the key to tables, columns and identifiers records
  • Where the copies are stored and who is custodian
  • Who may open it, as approved by a partner
  • Which look-ups staff must be able to do unaided
  • Retention period and the date it is next reviewed

Questions

BlueDot to Full data export: 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 Full data export 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 Full data export?

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 Full data export is kept as a readable archive, and you see which before the move.

What has to be decided before BlueDot is written out to Full data export?

Emails, custom fields, templates and intake records 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 Full data export are the names and marks of their owners, used here only to identify the two systems.

Moving from BlueDot to Full data export?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.