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

Data migration route

Salesforce to SimpleLaw migration

Salesforce is a cloud CRM and intake system, and SimpleLaw is a cloud practice management system. Contacts and intake history move, and the matters themselves start life in SimpleLaw.

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

What moves

What moves from Salesforce to SimpleLaw

Each row is a kind of record Salesforce holds, whether SimpleLaw has a place for it, and what is planned. On this route six kinds of record carry across, two kinds need mapping and one kind is confirmed in the analysis.

Records in Salesforce and their place in SimpleLaw
RecordIn SalesforceIn SimpleLawWhat is planned
ContactsClients, other parties and referrersHeldAccounts and contacts, or person accounts for individuals. Leads are separate.Has a placeAs leads, clients or other contacts in the CRM.Carried across
DocumentsFiles stored in or linked from the systemHeld in partSalesforce Files and older attachments linked to records.Has a placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails captured to a record are held as activity data.To be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesHeldNotes on records.Has a placeCarried across
CalendarAppointments, court dates and deadlinesHeld in partEvents are activities on records.Has a placeCarried 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 placeCarried with mapping
TemplatesPrecedents, document templates and automationHeld in partQuote templates.Has a place in partTemplates are rebuilt using SimpleLaw’s own automation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLeads, opportunities and campaign members.Has a placeLeads and intake forms.Carried across

What the plans mean

Carried across
SimpleLaw has a place for this kind of record. It is loaded there and checked against Salesforce.
Carried with mapping
SimpleLaw 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

Contacts and enquiries move. Matters begin in the new system.

A CRM knows people: who enquired, who referred them, what was sent and when. It does not know matters the way a practice system does. So the move from Salesforce to SimpleLaw is mostly a contacts job, and contacts are where duplicates live. The same person appears as a lead, a client and a referrer, sometimes under three email addresses. They are merged before extraction where they can be identified, because SimpleLaw will invoice and receipt against these records.

Pipelines, campaigns and automations seldom have a direct equivalent in a practice system. Open enquiries can be loaded as contacts with a note of their stage, or opened as matters if the firm wants them worked from the first day. Intake forms and email sequences are set up again in whatever SimpleLaw or its intake tool provides. Past correspondence is kept as notes or documents on the contact, so the history of a relationship can still be read.

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 SimpleLaw 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

Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.

  1. Lead, client or contact

    A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.

  2. Billing type on each matter

    Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.

  3. Storage chosen before loading

    If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.

  4. Custom fields named for templates

    Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.

  5. Portal access client by client

    The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.

More about moving into SimpleLaw

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in SimpleLaw 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 SimpleLaw. 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 SimpleLaw 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 toSimpleLaw

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

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

The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.

Set-up decisions in SimpleLaw

  • Labels for documents, activities, expenses and contact IDs
  • Custom fields and intake forms for each practice area
  • Document templates and the attorney-client agreement
  • Workflows for case types that follow a standard process
  • User permission sets and client portal visibility
  • QuickBooks connection and the online payment processor

Questions

Salesforce to SimpleLaw: 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 SimpleLaw?

SimpleLaw stores documents. Uploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.

Does everything in Salesforce have a place in SimpleLaw?

Most of it does on paper. Emails 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 SimpleLaw is kept as a readable archive, and you see which before the move.

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

Custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails are confirmed in the analysis. 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 SimpleLaw are the names and marks of their owners, used here only to identify the two systems.

Moving from Salesforce to SimpleLaw?

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

We reply within one business day.