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

Data migration route

BlueDot to Lawmatics migration

BlueDot is a cloud case management system for immigration work, and Lawmatics is a cloud CRM and intake system. This route carries people and their history into Lawmatics, and the table shows how much of the firm’s files and money has a place there.

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

What moves

What moves from BlueDot to Lawmatics

Each row is a kind of record BlueDot holds, whether Lawmatics has a place for it, and what is planned. On this route six kinds of record carry across, six kinds need mapping and one kind is confirmed in the analysis.

Records in BlueDot and their place in Lawmatics
RecordIn BlueDotIn LawmaticsWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldImmigration cases linked to contacts and employers.Has a placeLoaded from CSV with a status of PNC, Hired or Lost and a pipeline stage.Carried across
ContactsClients, other parties and referrersHeldForeign nationals with biographic and history records, and employers.Has a placeContacts and companies load from CSV; relationships link further parties to a matter.Carried across
DocumentsFiles stored in or linked from the systemHeldUploaded documents are stored encrypted; signed agreements save to the client file.Has a place in partFiles and folders on each matter, added by upload or API, not by the spreadsheet import.Carried 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 partEmails reach a matter through mail sync from a connected mailbox.Carried with mapping
NotesFile notes, matter notes and contact notesHeldNotes and reminders on contacts, including speech-to-text notes.Has a placeNotes on matters, contacts and companies.Carried across
CalendarAppointments, court dates and deadlinesHeldCalendar with two-way sync to Outlook 365 or Google Calendar.Has a placeAppointments, called events, with types and locations.Carried across
TasksTo-dos and workflow steps assigned to peopleHeld in partReminders are kept with notes.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeld in partTimesheets are listed among its advanced features.Has a place in partTime entries and expenses, where the Time & Billing module is enabled.Carried with mapping
BillingInvoices, payments and debtor balancesHeldInvoices, client balances, payment plans and online payment through PaySimple.Has a place in partInvoices and payments; a past invoice is entered as sent, then marked paid.Carried with mapping
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a place in partA trust account with a running balance; deposits are allocated to a contact and matter.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeld in partQuestionnaires are fully customisable.Has a placeMatter, contact and company fields. A field must exist before data is imported into it.Carried with mapping
TemplatesPrecedents, document templates and automationHeldUSCIS forms filled from questionnaire data, plus document assembly.Has a place in partDocument and email templates are rebuilt with Lawmatics merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partClient questionnaires gather biographic and case data.Has a placePipelines and stages, marketing sources and campaigns.Carried across

What the plans mean

Carried across
Lawmatics has a place for this kind of record. It is loaded there and checked against BlueDot.
Carried with mapping
Lawmatics 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

People and history move. Files and accounts stay.

A CRM wants to know who the firm knows and what has passed between them. From BlueDot that means contacts, their roles, their matters as a history of work done, and the referrers who sent them. Loaded into Lawmatics, a past client becomes someone the firm can contact again with that history in view. That is usually the reason for this route: the firm is adding an intake and marketing system beside its matter system, or replacing the front end of it.

A CRM is not usually where documents, time, billing and trust are kept, and the table above shows what Lawmatics takes. What it does not take stays in BlueDot or its successor. So the plan has to say which system is the master for a contact once both are running, or the two lists drift apart. Contacts are de-duplicated before the load, and anyone who has asked not to be contacted is flagged in Lawmatics from the first day.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of BlueDot depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to BlueDot is kept running until the checks on Lawmatics are finished.

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

Lawmatics takes matters, contacts and companies from CSV files, and its API accepts notes, tasks, appointments, files, time entries and invoices. It is an intake and client relationship system, so a firm arriving from full practice management has to decide what it is for. People and matters load well. There is no general ledger, and years of billing history have no natural home.

  1. Contacts and matters load separately

    The import expects two spreadsheets: one for contacts or companies with no case, such as referrers and other lawyers, and one for matters. A matter import creates the matter and its primary contact together. Every matter has exactly one primary contact, so joint clients are loaded as one primary and one relationship.

  2. Set up before loading

    Owner, stage, practice area, source and campaign are matched by name. A value on the spreadsheet that does not match one in Lawmatics exactly creates a new one, which is how a firm ends up with two spellings of the same practice area. Users, pipelines, practice areas and marketing sources are set up first, and custom fields must exist before data is loaded into them.

  3. Statuses and matter numbers

    Each imported matter must be PNC (potential new client), Hired or Lost, with open and closed handled as sub-statuses the firm creates. The case number is a system field assigned by an auto-numbering pattern and cannot be edited by hand afterwards. Whether old matter numbers can be loaded into it, or belong in a custom field, is tested in the trial load.

  4. Duplicates are matched by email

    With Match Contacts by Email switched on, a contact whose email already exists is skipped or updated, never doubled. Names and phone numbers are not checked. Matters are not deduplicated at all, so two rows with one email create two matters on one contact. Clean-up therefore happens in the spreadsheet, and automations are switched off for every load.

  5. What has no place

    There is no general ledger. The Time & Billing module holds time entries, expenses, invoices and a trust account with a running balance per matter, and past invoices are entered as already sent and then marked paid. A firm that needs its full accounting history keeps the old system read only or carries the books in an accounting package.

More about moving into Lawmatics

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover.

  1. Analysis

    We read what BlueDot holds and how its records link, then agree with you, field by field, where each piece will sit in Lawmatics. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in BlueDot, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Lawmatics as a trial and checked against BlueDot: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in BlueDot are frozen for an agreed window, the data is collected a final time and Lawmatics goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in BlueDot as at the cutover date. BlueDot 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 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 toLawmatics

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

Setting up Lawmatics

Loaded data is not yet a working system. This is what NewLaw sets up in Lawmatics, beyond the migration, so that people can work in it from the first day.

In Lawmatics the design comes before the data. The pipeline stages, practice areas, custom fields and relationship types decide what the import can hold, and the forms and automations decide what the firm’s intake looks like from the first day. If a practice system sits behind it, the field mapping between the two is part of the same job.

Set-up decisions in Lawmatics

  • Pipelines and stages for intake and for open matters
  • Practice areas, sub-statuses, relationship types and the matter numbering pattern
  • Custom fields on matters, contacts and companies
  • Intake forms, booking links and e-signature document templates
  • Follow-up automations, with marketing sources and campaigns
  • Mail and calendar sync, user roles and practice system integration

Questions

BlueDot to Lawmatics: 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.

Do trust balances in BlueDot have a place in Lawmatics?

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. If Lawmatics turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

Does everything in BlueDot have a place in Lawmatics?

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

What has to be decided before BlueDot data is loaded into Lawmatics?

Documents, emails, time entries, billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Trust ledgers are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.

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 Lawmatics are the names and marks of their owners, used here only to identify the two systems.

Moving from BlueDot to Lawmatics?

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

We reply within one business day.