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

Data migration route

HubSpot to LexWorkplace migration

HubSpot is a cloud CRM and intake system, and LexWorkplace is a cloud document management system. Only files and their details have a place there, so this route carries the documents and archives the rest.

FromHubSpotCloud
  1. Documents: Carried across
  2. Emails: Carried across
  3. Notes: Carried across
  4. Custom fields: Carried with mapping
  5. Templates: Carried with mapping
  6. Tasks: Confirmed in the analysis
ToLexWorkplaceCloud
  1. Contacts: Kept as a readable archive
  2. Calendar: Kept as a readable archive
  3. Billing: Kept as a readable archive
  4. Intake: Kept as a readable archive
Readable archiveNo place in LexWorkplace
  • 3 carried
  • 2 mapped
  • 1 to confirm
  • 4 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from HubSpot to LexWorkplace

Each row is a kind of record HubSpot holds, whether LexWorkplace has a place for it, and what is planned. On this route three kinds of record carry across, two kinds need mapping, four kinds have no place in LexWorkplace and are archived and one kind is confirmed in the analysis.

Records in HubSpot and their place in LexWorkplace
RecordIn HubSpotIn LexWorkplaceWhat is planned
ContactsClients, other parties and referrersHeldContacts and companies, linked by associations.No placeOnly a client name, status, attorneys and tags.Kept as a readable archive
DocumentsFiles stored in or linked from the systemHeld in partA files tool holds uploaded files. There are no matter folders.Has a placeFiled to a matter or to Firm Documents, in folders.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails logged to the CRM appear as activities on the record timeline.Has a placeOn the matter’s Email tab, in their own folders.Carried across
NotesFile notes, matter notes and contact notesHeldNotes are logged as activities on a record.Has a placeAs Matter Notes on the matter’s Notes tab.Carried across
CalendarAppointments, court dates and deadlinesHeld in partMeetings are logged as activities on records.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldTasks have their own export.To be confirmedConfirmed in the analysis
BillingInvoices, payments and debtor balancesHeld in partQuotes, invoices, payments and subscriptions exist as commerce records.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldCustom properties on every object, and custom objects.Has a place in partOld categories can become document types, statuses or tags.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partTemplates for marketing emails, pages and posts, not legal precedents.Has a place in partStored as files in Firm Documents.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldForms, lead and deal pipelines, segments and marketing email.No placeKept as a readable archive

What the plans mean

Carried across
LexWorkplace has a place for this kind of record. It is loaded there and checked against HubSpot.
Carried with mapping
LexWorkplace 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
LexWorkplace has no place for it. It is exported in a format that opens without HubSpot 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

Only the documents have a place here.

LexWorkplace is a document management system: it takes files and the details that describe them. Most of what HubSpot holds is not files. Entries, balances, settings and lists have no place in a document store, and the table above is short for that reason. What can move is any document HubSpot produced or stored: invoices as PDFs, signed agreements, attachments, exported reports. Each is filed under the client or matter it relates to.

The useful version of this job is often an archive. A firm retiring a system wants its records readable later without keeping the subscription or the old PC. The data is exported in open formats, spreadsheets and PDFs, and filed in LexWorkplace in a workspace set aside for it, with access limited to the people who need it. That gives the firm one place to look, under the same retention rules as the rest of its documents.

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

Where the data is now

HubSpot exports each object as its own spreadsheet: contacts, companies, deals and so on, with their properties and associations. The activity on those records, meaning the calls, notes and emails, is not in those files and has to be collected separately. A move is therefore two jobs: the records, and the history that hangs off them.

  1. Activities are a separate export

    A record export downloads current property values and associations. HubSpot’s own guidance is that contact activities such as calls and notes come from exporting individual contacts, from certain activity reports, or from the engagements API. Which of those routes suits a full history across thousands of contacts is settled in the analysis, and each timeline that is carried arrives as dated notes.

  2. Unsubscribes come with the contacts

    Exporting all contacts includes the people who have unsubscribed from all email. That is the firm’s record of who must not be emailed, and it has to survive the move. The unsubscribed flag is carried into whichever tool will send the firm’s mail next, before anything is sent from it.

  3. Deals standing in for matters

    Some law firms on HubSpot record each new enquiry as a deal and close it as won when the client signs. A won deal is roughly a matter opening, and a lost one is a declined enquiry. Deal stages are mapped to the destination’s intake statuses, and won deals are checked against existing matters so no client is created twice.

  4. Hundreds of properties, few used

    A HubSpot account gathers properties from every integration and form ever connected to it. Exporting all properties on records gives one column for each. The property list is exported first and checked for how many records hold a value in each, and only the fields the firm recognises are mapped.

  5. The website may live there

    Forms, landing pages and sometimes the whole website are built in HubSpot. If the firm is closing the account and not just moving its CRM data, pages, posts and files are exported as well, and the enquiry forms are rebuilt to feed the new system. HubSpot’s export guide lists each of these separately.

More about moving off HubSpot

Where it is going

LexWorkplace expects every document and email to belong to a matter, so loading it starts with the matter list: name, custom ID, client, type and dates. Uptime Legal states that it runs migration and onboarding for its customers itself. The preparation is getting the old system’s content into a clean client and matter structure, with the exceptions resolved, ready for that load.

  1. Matters carry little, by design

    A matter record holds a name, a custom ID, a client, a type, a location, assigned staff, tags and open and close dates. Parties, court details and financial data have no fields. Those stay in the practice management system, and the two are tied together by using the same matter number as the custom ID.

  2. Clients are only containers

    LexWorkplace says plainly that its clients are for grouping matters, not for client management. A client has a name, a status, primary attorneys and tags. Addresses, phone numbers and contact history from the old system are not loaded here. They go to the practice management system or stay behind.

  3. Three tabs per matter

    Content arrives as documents, emails or notes, each on its own tab with its own folders. Emails held as message files in an old folder tree have to be recognised and loaded as emails, not as documents, or they will not appear where lawyers look for correspondence.

  4. Closed matters and archive

    A matter is closed by giving it a close date, and closed matters can be moved to archive storage, where they keep their place but are not searched or indexed until un-archived. Old matters can therefore be loaded and archived straight away. The firm sets the cut-off year.

  5. Profiling is optional unless enforced

    Document type, status and tags are not required by default, though a firm can switch on mandatory profiling for matters. If the old system had document types, they are mapped to LexWorkplace types during the load. If it had none, the firm chooses between loading unprofiled and assigning types by folder name.

More about moving into LexWorkplace

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in LexWorkplace on this route, which makes it repeatable: a load can be run again until it is right. The maker of LexWorkplace says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in HubSpot and checking each trial against HubSpot.

  1. Analysis

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

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

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

Loaded data is not yet a working system. The maker of LexWorkplace runs or arranges the set-up of its product, so this is what has to be decided and put in place in LexWorkplace, whoever does the work, before people rely on it from the first day.

Setting LexWorkplace up for a firm is a short list of decisions made in its settings, plus software on each computer. The decisions are what the firm calls its matter types, document types and statuses, who can open which matters by default, and whether versioning is automatic or manual. The Launcher and the Outlook add-in are then installed for every user.

Set-up decisions in LexWorkplace

  • Matter types, document types, statuses and tag conventions
  • Groups, rights and default permissions for new matters
  • Automatic or manual versioning, and whether profiling is mandatory
  • Linking matters to Clio Manage where the firm uses it
  • Launcher, Office and Outlook add-ins on each Windows or Mac computer
  • A Firm Documents structure for templates, policies and internal files

Questions

HubSpot to LexWorkplace: what firms ask

Can we keep HubSpot for marketing and move only the client records?

Yes. Clients and matters go to the practice system, and HubSpot keeps sending newsletters and capturing enquiries. What matters then is the hand-over point: which system creates the contact first, and how a signed client passes from a deal to a matter without being keyed in twice.

Does the email history on each contact come across?

Emails logged to HubSpot’s timeline are activities, which sit outside the standard record export. HubSpot’s guidance names its API as one way to retrieve them, and once retrieved they can be loaded as correspondence notes against the client or matter. Emails that were never logged to HubSpot are still in the lawyers’ mailboxes and are outside this move.

Does billing history from HubSpot move into LexWorkplace?

No. LexWorkplace has no place for invoices or payments. Billing history from HubSpot is exported as reports and invoice copies and kept as a readable archive.

What happens to records LexWorkplace has no place for?

On this route that is contacts, calendar entries, billing records and intake records. They are exported from HubSpot 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 HubSpot data is loaded into LexWorkplace?

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

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

Moving from HubSpot to LexWorkplace?

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

We reply within one business day.