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

Data migration route

QuickBooks Desktop to SharePoint migration

QuickBooks Desktop is a desktop accounting and billing system, and SharePoint is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.

FromQuickBooks DesktopDesktop
  1. Matters: Carried with mapping
  2. Contacts: Carried with mapping
  3. Notes: Carried with mapping
  4. Tasks: Carried with mapping
  5. Templates: Carried with mapping
  6. Documents: Confirmed in the analysis
  7. Emails: Confirmed in the analysis
  8. Calendar: Confirmed in the analysis
  9. Custom fields: Confirmed in the analysis
ToSharePointCloud
  1. Time and expenses: Kept as a readable archive
  2. Billing: Kept as a readable archive
  3. Trust money: Kept as a readable archive
  4. Firm accounts: Kept as a readable archive
Readable archiveNo place in SharePoint
  • 5 mapped
  • 4 to confirm
  • 4 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from QuickBooks Desktop to SharePoint

Each row is a kind of record QuickBooks Desktop holds, whether SharePoint has a place for it, and what is planned. On this route five kinds need mapping, four kinds have no place in SharePoint and are archived and four kinds are confirmed in the analysis.

Records in QuickBooks Desktop and their place in SharePoint
RecordIn QuickBooks DesktopIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partNo matter record; clients and matters are kept as customers and customer jobs.Has a place in partAs a site, library, folder or list row the firm designs; no built-in matter record.Carried with mapping
ContactsClients, other parties and referrersHeldCustomers, vendors, employees and other names.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemTo be confirmedHas a placeFiles in libraries, with columns and versions.Confirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs .msg or .eml files, with columns for sender and date if set up.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeld in partNotes are one of the lists kept in the company file.Has a place in partAs documents, or as rows in a notes list if one is built.Carried with mapping
CalendarAppointments, court dates and deadlinesTo be confirmedHas a place in partPossible as a list; usually left in Outlook.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partA to-do list.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
Time and expensesTime and expense entries, billed and unbilledHeldTime against customers and jobs, billable or not.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldEstimates, invoices, credit memos and customer payments.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeld in partNo trust ledger; client funds are tracked through bank and liability accounts.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeldChart of accounts, vendor bills, checks, deposits and general journal entries.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeColumns and content types on libraries and lists.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partInvoice and form templates, which can be exported and imported.Has a place in partPrecedents as files; templates can be offered from a library.Carried with mapping

What the plans mean

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.
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
SharePoint has no place for it. It is exported in a format that opens without QuickBooks Desktop 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 QuickBooks Desktop 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 QuickBooks Desktop, 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.

QuickBooks Desktop runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. SharePoint is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.

Where the data is now

Leaving QuickBooks Desktop means either moving the firm’s books to another ledger, or moving the client and billing side into a practice system while the books continue somewhere else. Those are different jobs. In both, the company file is read list by list and transaction type by transaction type, and what the firm has improvised inside it for matters and trust is untangled first.

  1. Customers and jobs

    QuickBooks has customers and, beneath them, jobs. Some firms made each client a customer and each matter a job. Others made every matter its own customer, or never used jobs at all. The convention is worked out from the file itself, because it decides how clients and matters are rebuilt in a legal system.

  2. Trust held in ordinary accounts

    There is no trust ledger in the product. Firms record client money through a bank account and a liability account, sometimes with a sub-account or job per client. The balance per client is rebuilt from those postings and agreed to the trust bank reconciliation before it opens in the new system.

  3. Items drive the invoices

    Invoice lines are items, and each item points to an income account. Time is billed through service items with a rate. In a practice system those become activity codes and rates per lawyer. The item list is mapped line by line, since it carries both the wording clients saw and the account the income went to.

  4. One company file

    Everything is in a single company file that can be backed up and copied. Working from a copy leaves the live file alone during the analysis. After cutover the last backup and a working installation are kept so prior-year reports and audit queries can still be answered from the original.

  5. What Intuit’s own export covers

    Intuit documents exports of lists and transactions to Excel, CSV and its IIF format, and a separate route that moves lists to QuickBooks Online without transaction history. For a practice system the invoices, payments and unbilled time matter more than the lists, so the transaction detail is taken as well.

More about moving off QuickBooks Desktop

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 QuickBooks Desktop 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 QuickBooks Desktop: 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 QuickBooks Desktop, a final pass over a weekend picks up what changed since the trial. QuickBooks Desktop 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 QuickBooks Desktop 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 fromQuickBooks Desktop
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 QuickBooks Desktop 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

QuickBooks Desktop to SharePoint: what firms ask

Should we keep QuickBooks for the books and only move billing?

That is a common arrangement. A practice system takes over time, invoices and trust, and posts summary entries to the ledger. What has to be clear is which system owns receivables from the cutover date, so the same invoice is not counted in both. That line is drawn in the analysis.

Can Desktop transaction history go into another system?

Lists and open balances are the straightforward part. Full transaction history depends on the destination: a ledger will take journals and invoices, a practice system generally wants only matter-related billing. Years that are closed are usually left in the company file, which stays readable for as long as the firm keeps a working copy of the program.

We tracked matters as jobs. Is that usable?

It is the best case. Each job has a customer above it and its own invoices, payments and billable time, which is close to a matter. Job names are tidied in QuickBooks first, since they were often typed freely, and then become matter names or numbers.

Do trust balances in QuickBooks Desktop have a place in SharePoint?

No. SharePoint does not keep trust ledgers. Trust records from QuickBooks Desktop are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.

What happens to records SharePoint has no place for?

On this route that is time entries, billing records, trust ledgers and the firm’s accounts. They are exported from QuickBooks Desktop 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 QuickBooks Desktop data is loaded into SharePoint?

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

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

Moving from QuickBooks Desktop 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.