Data migration route
Salesforce to iManage Cloud migration
Salesforce 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.
SalesforceCloud- Documents: Carried across
- Emails: Carried across
- Custom fields: Carried with mapping
- Templates: Carried with mapping
iManage CloudCloud- Contacts: Kept as a readable archive
- Notes: Kept as a readable archive
- Calendar: Kept as a readable archive
- Tasks: Kept as a readable archive
- Intake: Kept as a readable archive
- 2 carried
- 2 mapped
- 5 archived
What moves
What moves from Salesforce to iManage Cloud
Each row is a kind of record Salesforce 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 five kinds have no place in iManage Cloud and are archived.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | HeldAccounts and contacts, or person accounts for individuals. Leads are separate. | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | Held in partSalesforce Files and older attachments linked to records. | 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 store | Held in partEmails captured to a record are held as activity data. | Has a placeLoaded as email documents into the workspace’s email folders. | Carried across |
| NotesFile notes, matter notes and contact notes | HeldNotes on records. | No placeFile notes can be loaded as documents on the matter. | Kept as a readable archive |
| CalendarAppointments, court dates and deadlines | Held in partEvents are activities on records. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | HeldTasks are activities on records. | No placeiManage Tracker is a separate product with its own set-up. | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields and custom objects, plus objects added by installed apps. | Has a place in partA fixed number of custom profile fields, each a validated list. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partQuote templates. | 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 pipelines | HeldLeads, opportunities and campaign members. | No place | Kept 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 Salesforce.
- 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 Salesforce 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 Salesforce 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 Salesforce 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 Salesforce 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 Salesforce is kept running until the checks on iManage Cloud are finished.
Where the data is now
Leaving Salesforce
Salesforce will hand over an entire org as a set of CSV files, one per object, through its Data Export service. Getting the data is rarely the problem. Understanding it is: which objects the firm really used, which fields were added by an app nobody remembers installing, and how records point to one another through their IDs.
The Data Export service
An administrator can export all data as a zip archive of CSV files, weekly or monthly depending on the edition, with options to include files, attachments and document versions. The archive is deleted 48 hours after it is ready, and a large org produces several zip files. Timing the final export around those limits is part of the cutover plan.
Formula fields are left out
Formula and roll-up summary fields are always excluded from exports, because they are calculated and not stored. A firm may rely on one without knowing it is a formula, such as a count of referrals from a contact. Those are identified in the analysis and either recalculated in the destination or captured through a report.
Accounts, contacts, person accounts
Salesforce separates the organisation, an account, from the people at it, contacts. Orgs that deal with individuals may use person accounts, which are both at once and appear in the account data and the contact data. Each client is resolved to one company or one person in the destination, with the record IDs used to avoid loading anyone twice.
Leads are not contacts
A lead is an enquiry kept in its own object, apart from accounts and contacts. Leads that never progressed are prospects the firm did not take on. They are moved to the destination’s intake area if it has one, kept as a marketing list, or left in the exported files.
Installed apps and legal layers
If the org runs a legal application built on the platform, the matters, parties and time entries live in that product’s custom objects, and its vendor’s documentation describes them. The move is then planned as a move off that product, with the standard Salesforce objects as supporting data.
Where it is going
Arriving in iManage Cloud
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.
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.
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.
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.
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.
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.
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.
Analysis
We read what Salesforce 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.
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.
Trial load
A trial is loaded into iManage Cloud and checked against Salesforce: 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.
Cutover
There is no financial cutover on this route. After a short freeze on changes in Salesforce, a final pass over a weekend picks up what changed since the trial. Salesforce 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 Salesforce 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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Salesforce 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.
- 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
Salesforce to iManage Cloud: what firms ask
How do we get a full copy of our Salesforce data?
From Setup, an administrator with the Weekly Data Export permission runs Data Export and chooses Include all data, ticking the options for files and attachments. Salesforce emails a link to one or more zip files. That copy is taken once for the analysis and again at cutover.
Do our custom objects come across?
They are exported like any other object. Whether they have a home depends on the destination. A custom object that tracks referrals may map to a referral field. One that models something the new system has no idea of is carried as notes or kept in the export files, and the firm sees which before the move.
Do documents from Salesforce keep their folders and dates in iManage Cloud?
iManage Cloud stores documents. Each needs a workspace and valid client and matter values; its class sets default security. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.
What happens to records iManage Cloud has no place for?
On this route that is contacts, notes, calendar entries, tasks and intake records. They are exported from Salesforce 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 Salesforce 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.
Other routes
Other routes from Salesforce and into iManage Cloud
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Salesforce and iManage Cloud are the names and marks of their owners, used here only to identify the two systems.
Moving from Salesforce 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.