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

Data migration route

Salesforce to Lawmatics migration

Salesforce and Lawmatics are each a cloud CRM and intake system. The records move, and the pipeline, forms and automations are set up again in Lawmatics.

FromSalesforceCloud
  1. Contacts: Carried across
  2. Notes: Carried across
  3. Calendar: Carried across
  4. Tasks: Carried across
  5. Intake: Carried across
  6. Documents: Carried with mapping
  7. Emails: Carried with mapping
  8. Custom fields: Carried with mapping
  9. Templates: Carried with mapping
ToLawmaticsCloud
  • 5 carried
  • 4 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Salesforce to Lawmatics

Each row is a kind of record Salesforce holds, whether Lawmatics has a place for it, and what is planned. On this route five kinds of record carry across and four kinds need mapping.

Records in Salesforce and their place in Lawmatics
RecordIn SalesforceIn LawmaticsWhat is planned
ContactsClients, other parties and referrersHeldAccounts and contacts, or person accounts for individuals. Leads are separate.Has a placeContacts and companies load from CSV; relationships link further parties to a matter.Carried across
DocumentsFiles stored in or linked from the systemHeld in partSalesforce Files and older attachments linked to records.Has a place in partFiles and folders on each matter, added by upload or API, not by the spreadsheet import.Carried with mapping
EmailsEmails saved to matters or to the storeHeld in partEmails captured to a record are held as activity data.Has a place in partEmails reach a matter through mail sync from a connected mailbox.Carried with mapping
NotesFile notes, matter notes and contact notesHeldNotes on records.Has a placeNotes on matters, contacts and companies.Carried across
CalendarAppointments, court dates and deadlinesHeld in partEvents are activities on records.Has a placeAppointments, called events, with types and locations.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTasks are activities on records.Has a placeCarried across
Custom fieldsFields and record types the firm added itselfHeldCustom fields and custom objects, plus objects added by installed apps.Has a placeMatter, contact and company fields. A field must exist before data is imported into it.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partQuote templates.Has a place in partDocument and email templates are rebuilt with Lawmatics merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLeads, opportunities and campaign members.Has a placePipelines and stages, marketing sources and campaigns.Carried across

What the plans mean

Carried across
Lawmatics has a place for this kind of record. It is loaded there and checked against Salesforce.
Carried with mapping
Lawmatics holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.

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

Contacts and leads move. Forms and automations are rebuilt.

Between two tools that manage contacts and enquiries, the records move cleanly and the machinery does not. Each pipeline stage in Salesforce needs an equivalent in Lawmatics, and stage names seldom line up. Open leads are loaded at the matching stage so that follow-up carries on. Closed and lost leads come across with their outcome, because conversion reporting depends on them. Sources and referrers are put into one list first.

Forms, email templates, sequences and automations are rebuilt by hand. It is worth doing on purpose: most firms find a sequence still running that nobody remembers setting up. Web forms and booking links on the firm’s site are repointed at cutover, and a test enquiry is put through each one. Consent and unsubscribe records move with the contacts and are checked separately, since a mistake there means emailing people who opted out.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Salesforce 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 Salesforce is kept running until the checks on Lawmatics are finished.

Where the data is now

Salesforce will hand over an entire org as a set of CSV files, one per object, through its Data Export service. Getting the data is rarely the problem. Understanding it is: which objects the firm really used, which fields were added by an app nobody remembers installing, and how records point to one another through their IDs.

  1. The Data Export service

    An administrator can export all data as a zip archive of CSV files, weekly or monthly depending on the edition, with options to include files, attachments and document versions. The archive is deleted 48 hours after it is ready, and a large org produces several zip files. Timing the final export around those limits is part of the cutover plan.

  2. Formula fields are left out

    Formula and roll-up summary fields are always excluded from exports, because they are calculated and not stored. A firm may rely on one without knowing it is a formula, such as a count of referrals from a contact. Those are identified in the analysis and either recalculated in the destination or captured through a report.

  3. Accounts, contacts, person accounts

    Salesforce separates the organisation, an account, from the people at it, contacts. Orgs that deal with individuals may use person accounts, which are both at once and appear in the account data and the contact data. Each client is resolved to one company or one person in the destination, with the record IDs used to avoid loading anyone twice.

  4. Leads are not contacts

    A lead is an enquiry kept in its own object, apart from accounts and contacts. Leads that never progressed are prospects the firm did not take on. They are moved to the destination’s intake area if it has one, kept as a marketing list, or left in the exported files.

  5. Installed apps and legal layers

    If the org runs a legal application built on the platform, the matters, parties and time entries live in that product’s custom objects, and its vendor’s documentation describes them. The move is then planned as a move off that product, with the standard Salesforce objects as supporting data.

More about moving off Salesforce

Where it is going

Lawmatics takes matters, contacts and companies from CSV files, and its API accepts notes, tasks, appointments, files, time entries and invoices. It is an intake and client relationship system, so a firm arriving from full practice management has to decide what it is for. People and matters load well. There is no general ledger, and years of billing history have no natural home.

  1. Contacts and matters load separately

    The import expects two spreadsheets: one for contacts or companies with no case, such as referrers and other lawyers, and one for matters. A matter import creates the matter and its primary contact together. Every matter has exactly one primary contact, so joint clients are loaded as one primary and one relationship.

  2. Set up before loading

    Owner, stage, practice area, source and campaign are matched by name. A value on the spreadsheet that does not match one in Lawmatics exactly creates a new one, which is how a firm ends up with two spellings of the same practice area. Users, pipelines, practice areas and marketing sources are set up first, and custom fields must exist before data is loaded into them.

  3. Statuses and matter numbers

    Each imported matter must be PNC (potential new client), Hired or Lost, with open and closed handled as sub-statuses the firm creates. The case number is a system field assigned by an auto-numbering pattern and cannot be edited by hand afterwards. Whether old matter numbers can be loaded into it, or belong in a custom field, is tested in the trial load.

  4. Duplicates are matched by email

    With Match Contacts by Email switched on, a contact whose email already exists is skipped or updated, never doubled. Names and phone numbers are not checked. Matters are not deduplicated at all, so two rows with one email create two matters on one contact. Clean-up therefore happens in the spreadsheet, and automations are switched off for every load.

  5. What has no place

    There is no general ledger. The Time & Billing module holds time entries, expenses, invoices and a trust account with a running balance per matter, and past invoices are entered as already sent and then marked paid. A firm that needs its full accounting history keeps the old system read only or carries the books in an accounting package.

More about moving into Lawmatics

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

    We read what Salesforce holds and how it is organised, then agree with you where each kind of record will sit in Lawmatics. 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 Lawmatics and checked against Salesforce: 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 Salesforce, a final pass over a weekend picks up what changed since the trial. Salesforce 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 Salesforce 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 fromSalesforce
Moving toLawmatics

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 Salesforce holds

    What is in it, how its records link, and where each piece would sit in Lawmatics. 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 Lawmatics

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

In Lawmatics the design comes before the data. The pipeline stages, practice areas, custom fields and relationship types decide what the import can hold, and the forms and automations decide what the firm’s intake looks like from the first day. If a practice system sits behind it, the field mapping between the two is part of the same job.

Set-up decisions in Lawmatics

  • Pipelines and stages for intake and for open matters
  • Practice areas, sub-statuses, relationship types and the matter numbering pattern
  • Custom fields on matters, contacts and companies
  • Intake forms, booking links and e-signature document templates
  • Follow-up automations, with marketing sources and campaigns
  • Mail and calendar sync, user roles and practice system integration

Questions

Salesforce to Lawmatics: what firms ask

How do we get a full copy of our Salesforce data?

From Setup, an administrator with the Weekly Data Export permission runs Data Export and chooses Include all data, ticking the options for files and attachments. Salesforce emails a link to one or more zip files. That copy is taken once for the analysis and again at cutover.

Do our custom objects come across?

They are exported like any other object. Whether they have a home depends on the destination. A custom object that tracks referrals may map to a referral field. One that models something the new system has no idea of is carried as notes or kept in the export files, and the firm sees which before the move.

Do documents from Salesforce keep their folders and dates in Lawmatics?

In part. Files and folders on each matter, added by upload or API, not by the spreadsheet import. The structure in Salesforce is mapped to what Lawmatics offers and you see the mapping before the load. File dates are carried.

Does everything in Salesforce have a place in Lawmatics?

On paper, yes: each kind of record Salesforce holds has a place in Lawmatics. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.

What has to be decided before Salesforce data is loaded into Lawmatics?

Documents, emails, custom fields and templates are carried with mapping, so each mapping is agreed with you first. 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

Salesforce and Lawmatics are the names and marks of their owners, used here only to identify the two systems.

Moving from Salesforce to Lawmatics?

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

We reply within one business day.