Data migration route
BlueDot to NetDocuments migration
BlueDot is a cloud case management system for immigration work, and NetDocuments 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.
BlueDotCloud- Documents: Carried across
- Emails: Carried across
- Matters: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Tasks: Confirmed in the analysis
- Trust money: Confirmed in the analysis
NetDocumentsCloud- Contacts: Kept as a readable archive
- Notes: Kept as a readable archive
- Calendar: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Intake: Kept as a readable archive
- 2 carried
- 3 mapped
- 2 to confirm
- 6 archived
What moves
What moves from BlueDot to NetDocuments
Each row is a kind of record BlueDot holds, whether NetDocuments has a place for it, and what is planned. On this route two kinds of record carry across, three kinds need mapping, six kinds have no place in NetDocuments and are archived and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldImmigration cases linked to contacts and employers. | Has a place in partAs a client and matter value with its workspace. Other matter details stay in practice management. | Carried with mapping |
| ContactsClients, other parties and referrers | HeldForeign nationals with biographic and history records, and employers. | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldUploaded documents are stored encrypted; signed agreements save to the client file. | Has a placeImported with profile values, folder, dates and access set per document. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partWith Office 365, emails to or copying a contact show in an Email Integration tab. | Has a placeLoaded as email items profiled to the matter. | Carried across |
| NotesFile notes, matter notes and contact notes | HeldNotes and reminders on contacts, including speech-to-text notes. | No placeFile notes are loaded as documents in the matter workspace. | Kept as a readable archive |
| CalendarAppointments, court dates and deadlines | HeldCalendar with two-way sync to Outlook 365 or Google Calendar. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | Held in partReminders are kept with notes. | To be confirmed | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | Held in partTimesheets are listed among its advanced features. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | HeldInvoices, client balances, payment plans and online payment through PaySimple. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | No place | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | Held in partQuestionnaires are fully customisable. | Has a placeAs custom profile attributes, created in the repository before the load. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldUSCIS forms filled from questionnaire data, plus document assembly. | Has a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partClient questionnaires gather biographic and case data. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- NetDocuments has a place for this kind of record. It is loaded there and checked against BlueDot.
- Carried with mapping
- NetDocuments 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
- NetDocuments 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. NetDocuments 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 NetDocuments 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 NetDocuments are finished.
Where the data is now
Leaving BlueDot
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in NetDocuments
Loading into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.
Lookup tables before documents
Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.
Workspaces come from the profile
A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.
Import files are unforgiving
The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.
Folder limits and depth
A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.
Security at the right level
Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in NetDocuments on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what BlueDot holds and how it is organised, then agree with you where each kind of record will sit in NetDocuments. Anything with no place there stays behind or is archived, and you see which before the move.
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.
Trial load
A trial is loaded into NetDocuments 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.
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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what BlueDot holds
What is in it, how its records link, and where each piece would sit in NetDocuments. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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 NetDocuments
Loaded data is not yet a working system. This is what NewLaw sets up in NetDocuments, beyond the migration, so that people can work in it from the first day.
Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.
Set-up decisions in NetDocuments
- Cabinet design: one for the firm, or several by purpose
- Profile attributes, lookup tables and the client and matter hierarchy
- Workspace layout with default folders, filters and saved searches
- User groups, cabinet membership and security for restricted matters
- A feed of new clients and matters from practice management
- ndOffice, ndMail and Outlook filing on every desk, with training
Questions
BlueDot to NetDocuments: 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 NetDocuments?
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 NetDocuments 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 NetDocuments has no place for?
On this route that is contacts, notes, calendar entries, 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 NetDocuments?
Matters, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Tasks and trust ledgers are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from BlueDot and into NetDocuments
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
BlueDot and NetDocuments are the names and marks of their owners, used here only to identify the two systems.
Moving from BlueDot to NetDocuments?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.