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

Data migration route

Keap to iManage Cloud migration

Keap is a cloud CRM and intake system, and iManage Cloud 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.

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

What moves

What moves from Keap to iManage Cloud

Each row is a kind of record Keap holds, whether iManage Cloud has a place for it, and what is planned. On this route two kinds of record carry across, two kinds need mapping and six kinds have no place in iManage Cloud and are archived.

Records in Keap and their place in iManage Cloud
RecordIn KeapIn iManage CloudWhat is planned
ContactsClients, other parties and referrersHeldContacts and companies, segmented by tags.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeld in partFiles can be uploaded to a contact record.Has a placeEach needs a workspace and valid client and matter values; its class sets default security.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 placeLoaded as email documents into the workspace’s email folders.Carried across
NotesFile notes, matter notes and contact notesHeldContact notes.No placeFile notes can be loaded as documents on the matter.Kept as a readable archive
CalendarAppointments, court dates and deadlinesHeld in partAppointments booked through the scheduler, synced with a Gmail or Outlook calendar.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldNo placeiManage Tracker is a separate product with its own set-up.Kept as a readable archive
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 place in partA fixed number of custom profile fields, each a validated list.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partEmail templates and automation sequences.Has a place in partPrecedents load as documents. Automation is rebuilt in the firm’s drafting tools.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
iManage Cloud has a place for this kind of record. It is loaded there and checked against Keap.
Carried with mapping
iManage Cloud 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
iManage Cloud 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

Only the documents have a place here.

iManage Cloud is a document management system: it takes files and the details that describe them. Most of what Keap 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 Keap 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 iManage Cloud 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 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 iManage Cloud 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

Administrators of an iManage Cloud library have API access only, so nothing is loaded by writing to a database. For cloudimanage.com, the newer of its two cloud platforms, iManage lists a supervised import API, sync APIs and a metadata loader. Nothing can be filed loose: every document goes into a workspace, with valid client and matter values. So the client and matter lists, the workspace template and the security groups are built first.

  1. Client and matter lists first

    Custom1 and custom2 are validated lists, with each matter a child of its client. A value that is not already in the list cannot be assigned to a document. The lists are loaded from the practice management system or the old document store before any content, closed matters with documents included.

  2. One workspace per matter

    Each matter gets a workspace generated from a template, so the template is designed before migration: its tabs, its folders, which are created up front and which on demand. Old folder trees rarely match it. The mapping says where each old folder lands and what happens to folders with no equivalent.

  3. Authors must be known users

    Author and operator are profile fields tied to users of the library. Documents written by people who left years ago need a decision: recreate those people as inactive users, or assign a placeholder author. That choice affects searching by author for as long as the firm uses the system.

  4. Hybrid security

    iManage calls its security model hybrid: where a user’s groups disagree, the most permissive access applies unless one of them is denied. On cloudimanage.com that model cannot be changed. Default security is normally set on the workspace and inherited below it. Restricted matters from the old system are loaded with their access list already in place.

  5. New numbers, original dates

    Documents are numbered by iManage as they are loaded, so old numbers do not carry over as numbers. On cloudimanage.com the file date setting is fixed to the file’s own date, and on imanage.work it can be set either way. Which dates display is checked on the trial load. The old reference can be carried in a custom field or the description where the firm wants to search by it.

More about moving into iManage Cloud

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in iManage Cloud 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 iManage Cloud. 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 iManage Cloud 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 toiManage Cloud

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 iManage Cloud. 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 iManage Cloud

Loaded data is not yet a working system. This is what NewLaw sets up in iManage Cloud, beyond the migration, so that people can work in it from the first day.

Setting up iManage Cloud is mostly design work done before any user logs in: how many libraries, what a workspace looks like, which profile fields are captioned for what, and who can see which matters. Then come the links that keep it running day to day, such as creating a workspace when a matter is opened in the practice management system, and the add-ins on each desk.

Set-up decisions in iManage Cloud

  • Library structure and captions for client, matter and other fields
  • Workspace templates, folder names and Flexible Folders rules by practice area
  • Document classes, subclasses and the profile fields each one requires
  • Roles, groups, default security and walls for restricted matters
  • Workspace creation fed from the practice management system’s matter list
  • Work Desktop, Outlook email filing and Mobility on each device, with training

Questions

Keap to iManage Cloud: 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 iManage Cloud?

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

On this route that is contacts, notes, calendar entries, tasks, 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 iManage Cloud?

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

Moving from Keap to iManage Cloud?

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

We reply within one business day.