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

Data migration route

Keap to SharePoint migration

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

FromKeapCloud
  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 Keap to SharePoint

Each row is a kind of record Keap 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 Keap and their place in SharePoint
RecordIn KeapIn SharePointWhat is planned
ContactsClients, other parties and referrersHeldContacts and companies, segmented by tags.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 partFiles can be uploaded to a contact record.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails sent from Keap, and one-to-one email synced with Gmail or Outlook.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 notesHeldContact notes.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 partAppointments booked through the scheduler, synced with a Gmail or Outlook calendar.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeldHas a place in partPossible as a list; no legal workflow built in.Carried with mapping
BillingInvoices, payments and debtor balancesHeld in partQuotes, one-off and recurring invoices, and card payments.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldCustom fields on contact and company records.Has a placeColumns and content types on libraries and lists.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partEmail templates and automation sequences.Has a place in partPrecedents as files; templates can be offered from a library.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldForms, landing pages, lead scoring and a sales pipeline.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 Keap.
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 Keap 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 Keap 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 Keap, 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 Keap 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 Keap is kept running until the checks on SharePoint are finished.

Where the data is now

Keap’s contact list is the easy part: it exports to a spreadsheet with standard and custom fields. The harder parts are the tags, which are how the account is organised and which the contact export leaves out, and the automations, which exist only as running sequences. Invoices and recurring payments need their own plan if clients are being charged through it.

  1. Tags are not in the export

    Keap’s contact export covers standard and custom fields but not tags. The vendor’s suggested method is to run the Tag Tracker report and match it to the exported contact IDs. Since tags usually record what a contact enquired about, where they came from and what they have been sent, that matching step cannot be skipped.

  2. Automations stop at cutover

    A contact halfway through a follow-up sequence will stop receiving it when the account is switched off. The automation history shows who is in which sequence. Sequences worth keeping are rebuilt in the destination, and contacts are placed at the equivalent step so nobody gets the welcome email twice.

  3. Recurring payments

    Where clients pay a retainer or subscription through Keap, the card details sit with the payment processor, not in a spreadsheet the firm can export. Each recurring charge is listed with its amount and next date, and the firm arranges new payment authorities in the new billing system before the old ones are cancelled.

  4. Email marketability status

    Each contact’s email address carries a marketability status showing whether marketing email may be sent to it. That status is the consent record. It is exported with the contact and applied in the new mailing tool, so that people who opted out years ago stay opted out.

More about moving off Keap

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

Keap to SharePoint: what firms ask

Is Keap the same as Infusionsoft?

Keap is the current name of the product and company that were called Infusionsoft, and some help pages still sit on the Infusionsoft domain. Thryv bought the company in 2024, and support articles now appear on Thryv’s site. For a move the name makes no difference: the account and its data are the same.

Can our contacts and their notes be exported together?

They come out as separate lists. Contacts export from the People view as a CSV, with larger exports sent as a download link by email. Notes and tags are reported on separately and joined back to each contact by its ID. The trial load checks that every note has landed on the right person.

Does billing history from Keap move into SharePoint?

No. SharePoint has no place for invoices or payments. Billing history from Keap 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 Keap 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 Keap 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

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

Moving from Keap 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.