Data migration route
LawLogix Immigration Case Management data to SQLite
LawLogix Immigration Case Management is a cloud case management system for immigration work, and SQLite 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 LawLogix Immigration Case Management holds and keeps it readable and open to queries.
LawLogix Immigration Case ManagementCloud- Matters: Exported in full
- Contacts: Exported in full
- Calendar: Exported in full
- Intake: Exported in full
- Documents: Exported with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Time and expenses: Confirmed in the analysis
- Billing: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
SQLiteFiles- Templates: Kept as a readable archive
- 4 carried
- 1 mapped
- 8 to confirm
- 1 archived
What moves
What moves from LawLogix Immigration Case Management to SQLite
Each row is a kind of record LawLogix Immigration Case Management holds, whether SQLite has a place for it, and what is planned. On this route four kinds of record carry across, one kind needs mapping, one kind has no place in SQLite and is archived and eight kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldImmigration cases, each following a workflow for its case type. | Has a placeA matters table keyed by matter number. | Exported in full |
| ContactsClients, other parties and referrers | HeldForeign nationals and employers, with HR users on their own portal. | Has a placeContacts and their roles on matters as linked tables. | Exported in full |
| DocumentsFiles stored in or linked from the system | HeldCase files and documents collected through the portals are stored digitally. | Has a place in partListed in a table; the files themselves stay in folders beside the database. | Exported with mapping |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partAs message files in folders, indexed in a table. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeA notes table linked to matters. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partDeadlines are monitored through reporting; a full calendar was not confirmed. | Has a placeA table of dated entries, with no calendar view. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a placeA table of tasks and their status at the final date. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | To be confirmed | Has a placeA table of time and expense entries. | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | To be confirmed | Has a placeInvoice and receipt tables; invoice PDFs kept as files. | Confirmed in the analysis |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a placeTrust transactions as rows, for look-up and not for accounting. | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | Has a placeLedger journals as rows, where the source held them. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeColumns added to the table they belonged to. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldQuestionnaires, forms and document lists set for each case type. | No placePrecedent files are kept in folders, not in the database. | Kept as a readable archive |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partForeign nationals complete a self-service intake through the portal. | Has a placeAn enquiries table, where the source tracked them. | Exported in full |
What the plans mean
- Exported in full
- SQLite has a place for this kind of record. It is loaded there and checked against LawLogix Immigration Case Management.
- Exported with mapping
- SQLite 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
- SQLite has no place for it. It is exported in a format that opens without LawLogix Immigration Case Management 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
Not a new system. A complete copy the firm can query.
Writing LawLogix Immigration Case Management out to SQLite 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 SQLite 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
Leaving LawLogix Immigration Case Management
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.
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.
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.
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.
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.
Where it is going
Arriving in SQLite
A SQLite archive suits a firm that wants the old system’s records kept, seldom consulted, and free of any server or subscription. Everything structured goes into one file. That simplicity moves the responsibility elsewhere: the file has no security of its own and no administrator watching it, so where it is stored and who can reach it are the real decisions.
One file, kept with the archive
Matters, contacts, time, invoices and trust transactions become tables in a single file. It is stored with the firm’s closed-matter records and can be copied like any document. A checksum recorded when the file is finalised lets anyone confirm, years later, that the copy they hold has not been altered, and the firm decides whether to keep one.
No logins inside the file
SQLite has no users or passwords. Anyone who can open the file can read every client’s ledger. Protection comes from where it is kept, such as a restricted folder or an encrypted volume, and that choice is the firm’s. It can suit an archive consulted by two people, and it is said plainly so nobody assumes otherwise.
Built for reading, not sharing
Only one program can write to the file at a time, and SQLite’s authors point people to a client/server database where many users share data over a network. A finished archive never meets that limit. It is the reason SQLite is used here for records that are closed and not for anything staff still update.
Documents stay outside it
Documents remain ordinary files in matter folders, and a table in the database lists each one with its matter, title, dates and path. Keeping them as files means they open with a double-click and can be handed to a client. The table is how a file is found by matter number instead of by guessing its name.
Someone has to open it
SQLite publishes its own command-line program for opening a database file, and other tools read the format too. None of that helps if nobody remembers how. Saved queries for the usual look-ups and a short note on which tool to use can sit in the same folder as the file, and the firm decides what it needs.
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.
Analysis
We read what LawLogix Immigration Case Management holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything LawLogix Immigration Case Management holds is in scope unless you take it out.
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.
Trial export
The data is written to SQLite 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.
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
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 LawLogix Immigration Case Management holds
What is in it, how its records link, and where each piece would sit in SQLite. 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
Structure, permissions and handover
SQLite 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.
There is nothing to install on a server and nothing to license. The work is in making the file usable and safe to keep: naming it, documenting its tables, storing it where the firm’s records policy says archives go, and checking that a member of staff can open it and find a matter. Whether a second copy is held somewhere separate is the firm’s call.
What is agreed and set up
- File name, storage location and whether a second copy exists
- Whether a checksum is recorded for later verification
- Saved queries for matter, ledger and document look-ups
- Which tool staff will use to open the file
- Who may open the folder the file sits in
- Retention period and destruction date noted beside the file
Questions
LawLogix Immigration Case Management to SQLite: 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 SQLite 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.
What happens to records SQLite has no place for?
On this route that is templates. They are exported from LawLogix Immigration Case Management 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 LawLogix Immigration Case Management is written out to SQLite?
Documents 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.
Other routes
Other routes from LawLogix Immigration Case Management and into SQLite
Other destinations from LawLogix Immigration Case Management
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.
LawLogix Immigration Case Management and SQLite are the names and marks of their owners, used here only to identify the two systems.
Moving from LawLogix Immigration Case Management to SQLite?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.