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

Data migration route

eimmigration by Cerenade data to SQLite

eimmigration by Cerenade 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 eimmigration by Cerenade holds and keeps it readable and open to queries.

Fromeimmigration by CerenadeCloud
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Notes: Exported in full
  4. Calendar: Exported in full
  5. Tasks: Exported in full
  6. Time and expenses: Exported in full
  7. Billing: Exported in full
  8. Trust money: Exported in full
  9. Intake: Exported in full
  10. Documents: Exported with mapping
  11. Emails: Exported with mapping
  12. Custom fields: Exported with mapping
  13. Firm accounts: Confirmed in the analysis
ToSQLiteFiles
  1. Templates: Kept as a readable archive
Readable archiveNo place in SQLite
  • 9 carried
  • 3 mapped
  • 1 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from eimmigration by Cerenade to SQLite

Each row is a kind of record eimmigration by Cerenade holds, whether SQLite has a place for it, and what is planned. On this route nine kinds of record carry across, three kinds need mapping, one kind has no place in SQLite and is archived and one kind is confirmed in the analysis.

Records in eimmigration by Cerenade and their place in SQLite
RecordIn eimmigration by CerenadeIn SQLiteWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases, each with a petition type, assigned forms, process steps and receipt numbers.Has a placeA matters table keyed by matter number.Exported in full
ContactsClients, other parties and referrersHeldClient profiles with biographic, family and employment history, plus prospects and leads.Has a placeContacts and their roles on matters as linked tables.Exported in full
DocumentsFiles stored in or linked from the systemHeldStored on client and case profiles; clients upload through the portal.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 storeHeld in partEmails can be logged on client and case profiles; texts and portal messages are kept too.Has a place in partAs message files in folders, indexed in a table.Exported with mapping
NotesFile notes, matter notes and contact notesHeldClient interaction notes, which can be shown to the client in the portal.Has a placeA notes table linked to matters.Exported in full
CalendarAppointments, court dates and deadlinesHeldAppointments and caseworker calendars, with Office 365 or Google Calendar sync.Has a placeA table of dated entries, with no calendar view.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldProcess steps, reminders and automated workflows for each case type.Has a placeA table of tasks and their status at the final date.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldCaseworker time tracked against each case and client profile.Has a placeA table of time and expense entries.Exported in full
BillingInvoices, payments and debtor balancesHeldInvoices, payment plans, expenses and payments.Has a placeInvoice and receipt tables; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeldThe vendor describes built-in trust accounting.Has a placeTrust transactions as rows, for look-up and not for accounting.Exported in full
Firm accountsGeneral ledger, office account and payablesTo be confirmedHas a placeLedger journals as rows, where the source held them.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom fields on client and case profiles.Has a placeColumns added to the table they belonged to.Exported with mapping
TemplatesPrecedents, document templates and automationHeldGovernment forms library, multilingual questionnaires, email and letter templates.No placePrecedent files are kept in folders, not in the database.Kept as a readable archive
IntakeLeads, enquiries, intake forms and pipelinesHeldLeads and prospects pipeline, website enquiry capture and intake questionnaires.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 eimmigration by Cerenade.
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 eimmigration by Cerenade 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 eimmigration by Cerenade 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 eimmigration by Cerenade 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.

eimmigration by Cerenade 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 eimmigration by Cerenade will release depends on its export tools, and that is confirmed in the analysis.

Where the data is now

Moving off eimmigration is mostly a question of where a very detailed client record goes. The system holds far more about each person than a general practice system has fields for, and it ties that data to government forms. Cases, documents, invoices and trust balances have ordinary homes. The biographic data, the questionnaires and the form answers need a decision each.

  1. A profile deeper than a contact

    Each client profile carries biographic, family, professional and historical data, plus copies of passports, I-94s and birth certificates. A general practice system gives a contact a name, an address and a few custom fields. The analysis lists every profile field in use and decides which become custom fields, which become a summary document on the matter, and which stay behind.

  2. Forms are data, not files

    The government forms are filled from answers held in the system, so one address change updates every form. Outside an immigration product those answers have no engine to feed. Filed forms are carried as PDFs on the case. The answers behind them move only where the destination has a matching field or its own forms library.

  3. Expiry dates and receipt numbers

    Cases are found by receipt or notice number, and the system watches passport, visa and I-94 expiry dates up to 180 days ahead. Those dates are worth more than most of the record. Each one needs a date field in the new system that can raise a reminder, because a date sitting inside a note warns nobody.

  4. Family members share a file

    The system shows every case and service for a client together with their associated family members. A spouse and children on one petition are separate people linked to one another. The links are checked in the trial load by opening known families and confirming that each member still reaches the same cases.

  5. Payment plans and trust

    Invoices, payment plans, expenses and trust accounting are inside the product, with card payments taken through Braintree or LawPay. A client halfway through a payment plan has a schedule and a balance. The balance moves as an opening figure. The schedule and any automatic card payments are set up again in the new system before the old ones are switched off.

More about moving off eimmigration by Cerenade

Where it is going

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.

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

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

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

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

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

More about moving into SQLite

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 eimmigration by Cerenade holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything eimmigration by Cerenade 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 SQLite as a trial and checked against eimmigration by Cerenade: record counts, totals where eimmigration by Cerenade 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 eimmigration by Cerenade, the export is run a final time and checked again. There is nothing to go live. eimmigration by Cerenade 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 eimmigration by Cerenade 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 fromeimmigration by Cerenade
Moving toSQLite

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 eimmigration by Cerenade 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.

  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

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

eimmigration by Cerenade to SQLite: what firms ask

Will our clients’ immigration forms come across as forms?

As documents, yes. Each completed form is carried as a PDF on the client’s case. As live forms that refill from the client’s data, only if the new system is an immigration product with its own forms library. Which of the two applies to your destination is settled in the analysis, before anything is extracted.

What happens to the client portal?

Portal logins do not move. What clients put there does: uploaded documents, questionnaire answers and the notes you chose to show them are all part of the case record. If the new system has a portal, clients are invited to it after cutover, and the firm decides what they should see on day one.

Can we bring archived and closed cases?

Yes. eimmigration keeps active, archived and closed cases apart, and each status is carried across as it stands. Immigration clients come back years later for a renewal or a naturalisation, which is a reason to bring every case. If older ones are left behind, they remain in the read-only copy of the old system.

Does the copy in SQLite hold trust ledgers from eimmigration by Cerenade?

Yes. Trust transactions as rows, for look-up and not for accounting. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in eimmigration by Cerenade as at the export date.

What happens to records SQLite has no place for?

On this route that is templates. They are exported from eimmigration by Cerenade 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 eimmigration by Cerenade is written out to SQLite?

Documents, emails and custom fields are exported with mapping, so each mapping is agreed with you first. The firm’s accounts 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

eimmigration by Cerenade and SQLite are the names and marks of their owners, used here only to identify the two systems.

Moving from eimmigration by Cerenade 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.