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

Data migration route

LawLogix Immigration Case Management data to Microsoft SQL Server

LawLogix Immigration Case Management 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 LawLogix Immigration Case Management holds and keeps it readable and open to queries.

FromLawLogix Immigration Case ManagementCloud
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Calendar: Exported in full
  4. Intake: Exported in full
  5. Documents: Exported with mapping
  6. Templates: Exported with mapping
  7. Emails: Confirmed in the analysis
  8. Notes: Confirmed in the analysis
  9. Tasks: Confirmed in the analysis
  10. Time and expenses: Confirmed in the analysis
  11. Billing: Confirmed in the analysis
  12. Trust money: Confirmed in the analysis
  13. Firm accounts: Confirmed in the analysis
  14. Custom fields: Confirmed in the analysis
ToMicrosoft SQL ServerServer
  • 4 carried
  • 2 mapped
  • 8 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from LawLogix Immigration Case Management to Microsoft SQL Server

Each row is a kind of record LawLogix Immigration Case Management holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route four kinds of record carry across, two kinds need mapping and eight kinds are confirmed in the analysis.

Records in LawLogix Immigration Case Management and their place in Microsoft SQL Server
RecordIn LawLogix Immigration Case ManagementIn Microsoft SQL ServerWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldImmigration cases, each following a workflow for its case type.Has a placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeldForeign nationals and employers, with HR users on their own portal.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldCase files and documents collected through the portals are stored digitally.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 storeTo be confirmedHas a place in partAs message files with an index table, or as rows of header fields.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeRows of text linked to matters and contacts.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partDeadlines are monitored through reporting; a full calendar was not confirmed.Has a placeRows of appointments and key dates; nothing displays them as a calendar.Exported in full
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeRows with assignee, due date and status.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledTo be confirmedHas a placeTime and expense rows with rates and billed status.Confirmed in the analysis
BillingInvoices, payments and debtor balancesTo be confirmedHas a placeInvoices, lines and receipts as rows; invoice PDFs kept as files.Confirmed in the analysis
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
Firm accountsGeneral ledger, office account and payablesTo be confirmedHas a placeGeneral ledger journals and balances, where the source held them.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeAs added columns, or a table of field names and values.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldQuestionnaires, forms and document lists set for each case type.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partForeign nationals complete a self-service intake through the portal.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 LawLogix Immigration Case Management.
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 LawLogix Immigration Case Management 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 LawLogix Immigration Case Management 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.

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

Where the data is now

A firm on LawLogix has its immigration cases in one product and, quite often, a client’s I-9 records in a sister product that is not part of the same data. The move is planned around the foreign national: who they are, who sponsors them, what has been filed and what expires when. Billing and accounting detail is confirmed in the analysis because the vendor does not publish it.

  1. The foreign national comes first

    Records are organised around the foreign national and then the employer, not around a client and a matter number. A law firm’s destination system will usually want the paying client at the top. The analysis sets which party becomes the client on each case and how the other is linked, so searches by either name still work.

  2. Guardian is a separate product

    LawLogix also sells Guardian for Form I-9 and E-Verify. Employers often hold both, and staff may speak of them as one system. I-9 records are not immigration case data and do not travel with it. The scope is written down at the start so nobody expects employment verification history to appear in the new case system.

  3. Workflows differ by case type

    Each case type has its own set of questionnaires, forms and documents to gather, delivered to the client as a personal checklist. A case in progress is partway through that list. What has been received and what is outstanding is carried as the status of each item, since a bare list of documents does not show what is missing.

  4. Two portals to replace

    Foreign nationals and employers each have a portal for answering questions, uploading documents and reading case updates. The portals are part of LawLogix and do not move. Everything already submitted is part of the case record and moves with it. How clients send documents after go-live is decided before cutover, and they are told once.

More about moving off LawLogix Immigration Case Management

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

LawLogix Immigration Case Management to Microsoft SQL Server: what firms ask

We know it as Edge. Is that the same system?

As far as the public record shows, yes. LawLogix’s immigration product has been listed and reviewed under the name Edge, and Equifax now calls it Immigration Case Management. The analysis starts from the firm’s own account and the screens staff use every day, so the name on the contract does not change the work.

Do the completed forms and receipt notices move?

They move as documents on each case, with their dates. The answers that produced the forms are data inside LawLogix and are mapped separately. Where the new system has matching fields the answers are loaded into them. Where it does not, the firm chooses between custom fields and a summary sheet filed on the matter.

What about our I-9 records in Guardian?

They are outside an immigration case migration. Guardian is a different product with its own data, and I-9 forms have their own retention rules. If an employer is changing I-9 systems too, that is planned as a separate piece of work with its own checks, and it should not share a cutover weekend.

Does the copy in Microsoft SQL Server hold trust ledgers from LawLogix Immigration Case Management?

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 LawLogix Immigration Case Management before the plan is fixed.

Does everything in LawLogix Immigration Case Management have a place in Microsoft SQL Server?

Most of it does on paper. Emails, notes, tasks, time entries, billing records, trust ledgers, the firm’s accounts and custom fields 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 LawLogix Immigration Case Management is written out to Microsoft SQL Server?

Documents and templates are exported with mapping, so each mapping is agreed with you first. Emails, notes, tasks, time entries, billing records, trust ledgers, the firm’s accounts and custom fields 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

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

Moving from LawLogix Immigration Case Management 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.