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

Data migration route

HubSpot to SharePoint migration

HubSpot is a cloud CRM and intake system, and SharePoint is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.

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

What moves

What moves from HubSpot to SharePoint

Each row is a kind of record HubSpot holds, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across, seven kinds need mapping and two kinds have no place in SharePoint and are archived.

Records in HubSpot and their place in SharePoint
RecordIn HubSpotIn SharePointWhat is planned
ContactsClients, other parties and referrersHeldContacts and companies, linked by associations.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeld in partA files tool holds uploaded files. There are no matter folders.Has a placeFiles in libraries, with columns and versions.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 place in partAs .msg or .eml files, with columns for sender and date if set up.Carried with mapping
NotesFile notes, matter notes and contact notesHeldNotes are logged as activities on a record.Has a place in partAs documents, or as rows in a notes list if one is built.Carried with mapping
CalendarAppointments, court dates and deadlinesHeld in partMeetings are logged as activities on records.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeldTasks have their own export.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
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 placeColumns and content types on libraries and lists.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partTemplates for marketing emails, pages and posts, not legal precedents.Has a place in partPrecedents as files; templates can be offered from a library.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
SharePoint has a place for this kind of record. It is loaded there and checked against HubSpot.
Carried with mapping
SharePoint holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
Kept as a readable archive
SharePoint 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

An export the firm can open without the system.

SharePoint holds files, and most of what HubSpot holds is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used HubSpot, by client or by year, with a short index file saying what is where.

Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in SharePoint is limited before the export is copied in.

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

SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.

  1. Site, library or folder per matter

    A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.

  2. Columns are built before content

    If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.

  3. The 400 character path

    SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.

  4. Large libraries and the view threshold

    A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.

  5. Security by library, not by file

    Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.

More about moving into SharePoint

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

    We read what HubSpot holds and how it is organised, then agree with you where each kind of record will sit in SharePoint. 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 SharePoint 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 toSharePoint

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

SharePoint is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.

What is agreed and set up

  • Site and library structure for clients and matters
  • Columns and content types for matter number and document type
  • Permission groups, with restricted matters in their own libraries
  • A repeatable way to create each new matter’s workspace
  • Version history limits and retention labels for closed matters
  • Views, indexed columns and search tested on loaded data

Questions

HubSpot to SharePoint: 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 SharePoint?

No. SharePoint 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 SharePoint has no place for?

On this route that is 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 SharePoint?

Contacts, emails, notes, calendar entries, tasks, 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

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

Moving from HubSpot to SharePoint?

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

We reply within one business day.