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

Data migration route

HubSpot to Sync.com migration

HubSpot is a cloud CRM and intake system, and Sync.com 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. Emails: Carried with mapping
  3. Notes: Carried with mapping
  4. Templates: Carried with mapping
ToSync.comCloud
  1. Contacts: Kept as a readable archive
  2. Calendar: Kept as a readable archive
  3. Tasks: Kept as a readable archive
  4. Billing: Kept as a readable archive
  5. Custom fields: Kept as a readable archive
  6. Intake: Kept as a readable archive
Readable archiveNo place in Sync.com
  • 1 carried
  • 3 mapped
  • 6 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from HubSpot to Sync.com

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

Records in HubSpot and their place in Sync.com
RecordIn HubSpotIn Sync.comWhat is planned
ContactsClients, other parties and referrersHeldContacts and companies, linked by associations.No placeKept 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 placeFiles and folders within the path limit; some file types are skipped by the apps.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 partMessage files such as .msg or .eml, filed in the matter’s folder.Carried with mapping
NotesFile notes, matter notes and contact notesHeldNotes are logged as activities on a record.Has a place in partOnly as a document written out to the matter’s folder.Carried with mapping
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.No placeKept as a readable archive
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.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationHeld in partTemplates for marketing emails, pages and posts, not legal precedents.Has a place in partPrecedents load as ordinary files.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
Sync.com has a place for this kind of record. It is loaded there and checked against HubSpot.
Carried with mapping
Sync.com 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
Sync.com 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.

Sync.com 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 Sync.com 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 Sync.com 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

A firm that moves its files to Sync is usually doing so for confidentiality, and the load has to respect how the service is built to deliver it. Files are encrypted before they leave the computer. Nobody at Sync can look inside the account to confirm what arrived, so the checking is done from the firm’s side, against the list of what was sent.

  1. Files or Vault

    Open matters belong in Files, where they sync to the people working on them. Closed matters can go to Vault, which holds them in the cloud without putting a copy on every laptop. The firm supplies its open and closed matter lists so each folder is sent to the right side.

  2. A 248 character path limit

    Sync sets a maximum path length of 248 characters to stay compatible between Windows and Mac, and its apps skip anything longer. That is tighter than most systems a firm will be coming from. Folder names are shortened in the plan, and Sync’s own guidance favours a tree only a few levels deep.

  3. What the apps leave out

    The desktop apps do not upload shortcut files, temporary Office files or names containing a slash, and they warn against several other characters on Windows. A copy to Vault produces a transfer report listing what was skipped. That report is reconciled against the source file list after every load.

  4. Permissions come from the top folder

    Sharing is set on a folder and flows down to all of its contents. A matter that needs different access from the rest of a client’s work cannot simply sit one level down with tighter settings. It becomes its own shared folder, and those exceptions are identified before the tree is built.

  5. Shared folders count against storage

    A shared folder is added to each member’s account and normally counts towards their quota, and it syncs to their computer as a real folder. Sharing the whole client tree with every person can fill both. Shares are sized to teams, and the allowance needed per user is worked out from the document volumes.

More about moving into Sync.com

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Sync.com 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 Sync.com. 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 Sync.com 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 toSync.com

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 Sync.com. 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

Sync.com 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.

A Sync set-up comes down to accounts and shares. A team plan gives an administrator control over users, two-factor authentication and password resets, which matters more than usual in a service the provider says it cannot see into. The shared folders are then created to match the firm’s teams and its restricted matters.

What is agreed and set up

  • Administrator account and a user for each staff member
  • Two-factor authentication enforced across the firm
  • Team shared folders with view or edit permission per person
  • Which matters live in Files and which in Vault
  • Rules for client links: passwords, expiry dates, upload rights
  • Desktop app installed, with a filing guide for new matters

Questions

HubSpot to Sync.com: 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 Sync.com?

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

On this route that is contacts, calendar entries, tasks, billing records, custom fields 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 Sync.com?

Emails, notes 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 Sync.com are the names and marks of their owners, used here only to identify the two systems.

Moving from HubSpot to Sync.com?

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

We reply within one business day.