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

Data migration route

BlueDot to iManage Cloud migration

BlueDot is a cloud case management system for immigration work, and iManage Cloud is a cloud document management system. Documents and email move, filed under the matters they came from. Time, billing and trust have no place in a document system.

FromBlueDotCloud
  1. Documents: Carried across
  2. Emails: Carried across
  3. Matters: Carried with mapping
  4. Custom fields: Carried with mapping
  5. Templates: Carried with mapping
  6. Trust money: Confirmed in the analysis
ToiManage CloudCloud
  1. Contacts: Kept as a readable archive
  2. Notes: Kept as a readable archive
  3. Calendar: Kept as a readable archive
  4. Tasks: Kept as a readable archive
  5. Time and expenses: Kept as a readable archive
  6. Billing: Kept as a readable archive
  7. Intake: Kept as a readable archive
Readable archiveNo place in iManage Cloud
  • 2 carried
  • 3 mapped
  • 1 to confirm
  • 7 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from BlueDot to iManage Cloud

Each row is a kind of record BlueDot holds, whether iManage Cloud has a place for it, and what is planned. On this route two kinds of record carry across, three kinds need mapping, seven kinds have no place in iManage Cloud and are archived and one kind is confirmed in the analysis.

Records in BlueDot and their place in iManage Cloud
RecordIn BlueDotIn iManage CloudWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldImmigration cases linked to contacts and employers.Has a place in partAs a workspace with client and matter metadata. Parties and status stay in practice management.Carried with mapping
ContactsClients, other parties and referrersHeldForeign nationals with biographic and history records, and employers.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldUploaded documents are stored encrypted; signed agreements save to the client file.Has a placeEach needs a workspace and valid client and matter values; its class sets default security.Carried across
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 placeLoaded as email documents into the workspace’s email folders.Carried across
NotesFile notes, matter notes and contact notesHeldNotes and reminders on contacts, including speech-to-text notes.No placeFile notes can be loaded as documents on the matter.Kept as a readable archive
CalendarAppointments, court dates and deadlinesHeldCalendar with two-way sync to Outlook 365 or Google Calendar.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeld in partReminders are kept with notes.No placeiManage Tracker is a separate product with its own set-up.Kept as a readable archive
Time and expensesTime and expense entries, billed and unbilledHeld in partTimesheets are listed among its advanced features.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldInvoices, client balances, payment plans and online payment through PaySimple.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesTo be confirmedNo placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeld in partQuestionnaires are fully customisable.Has a place in partA fixed number of custom profile fields, each a validated list.Carried with mapping
TemplatesPrecedents, document templates and automationHeldUSCIS forms filled from questionnaire data, plus document assembly.Has a place in partPrecedents load as documents. Automation is rebuilt in the firm’s drafting tools.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partClient questionnaires gather biographic and case data.No placeKept as a readable archive

What the plans mean

Carried across
iManage Cloud has a place for this kind of record. It is loaded there and checked against BlueDot.
Carried with mapping
iManage Cloud 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.
Kept as a readable archive
iManage Cloud has no place for it. It is exported in a format that opens without BlueDot and handed to the firm as a read-only archive.

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

The documents move. The accounts do not.

Moving from a matter system into a document management system is a documents job. iManage Cloud has no place for time, invoices or trust, so there is no financial cutover on this route. What it does want is structure. Every document from BlueDot is filed into a workspace or folder for its client and matter, with a profile that says what it is. The client and matter list becomes that structure, which is why it is cleaned before any file is copied.

A document’s own details count for more here than anywhere. Created and modified dates, author, document type and version become searchable profile fields, and a wrong date on a few thousand files is hard to undo. Email filed to matters is carried as messages. Document copies can be run again, so the trial is repeated until counts and dates agree. Matter data that iManage Cloud cannot hold goes to whatever replaces BlueDot for matters and billing, or into an archive.

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 iManage Cloud 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

Administrators of an iManage Cloud library have API access only, so nothing is loaded by writing to a database. For cloudimanage.com, the newer of its two cloud platforms, iManage lists a supervised import API, sync APIs and a metadata loader. Nothing can be filed loose: every document goes into a workspace, with valid client and matter values. So the client and matter lists, the workspace template and the security groups are built first.

  1. Client and matter lists first

    Custom1 and custom2 are validated lists, with each matter a child of its client. A value that is not already in the list cannot be assigned to a document. The lists are loaded from the practice management system or the old document store before any content, closed matters with documents included.

  2. One workspace per matter

    Each matter gets a workspace generated from a template, so the template is designed before migration: its tabs, its folders, which are created up front and which on demand. Old folder trees rarely match it. The mapping says where each old folder lands and what happens to folders with no equivalent.

  3. Authors must be known users

    Author and operator are profile fields tied to users of the library. Documents written by people who left years ago need a decision: recreate those people as inactive users, or assign a placeholder author. That choice affects searching by author for as long as the firm uses the system.

  4. Hybrid security

    iManage calls its security model hybrid: where a user’s groups disagree, the most permissive access applies unless one of them is denied. On cloudimanage.com that model cannot be changed. Default security is normally set on the workspace and inherited below it. Restricted matters from the old system are loaded with their access list already in place.

  5. New numbers, original dates

    Documents are numbered by iManage as they are loaded, so old numbers do not carry over as numbers. On cloudimanage.com the file date setting is fixed to the file’s own date, and on imanage.work it can be set either way. Which dates display is checked on the trial load. The old reference can be carried in a custom field or the description where the firm wants to search by it.

More about moving into iManage Cloud

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in iManage Cloud on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what BlueDot holds and how it is organised, then agree with you where each kind of record will sit in iManage Cloud. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into iManage Cloud and checked against BlueDot: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in BlueDot, a final pass over a weekend picks up what changed since the trial. 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 toiManage Cloud

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 iManage Cloud. 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 iManage Cloud

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

Setting up iManage Cloud is mostly design work done before any user logs in: how many libraries, what a workspace looks like, which profile fields are captioned for what, and who can see which matters. Then come the links that keep it running day to day, such as creating a workspace when a matter is opened in the practice management system, and the add-ins on each desk.

Set-up decisions in iManage Cloud

  • Library structure and captions for client, matter and other fields
  • Workspace templates, folder names and Flexible Folders rules by practice area
  • Document classes, subclasses and the profile fields each one requires
  • Roles, groups, default security and walls for restricted matters
  • Workspace creation fed from the practice management system’s matter list
  • Work Desktop, Outlook email filing and Mobility on each device, with training

Questions

BlueDot to iManage Cloud: 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 iManage Cloud?

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

What happens to records iManage Cloud has no place for?

On this route that is contacts, notes, calendar entries, tasks, time entries, billing records and intake records. They are exported from BlueDot in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

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

Matters, 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 decides which closed matters and how many versions of a document are in scope.

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

Moving from BlueDot to iManage Cloud?

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

We reply within one business day.