Salesforce · iManage Data Quality

iManage data cleansing services for cleaner workspace metadata

iManage data cleansing services correct the inaccurate, incomplete, outdated and inconsistent Salesforce values that become iManage workspace names and profile metadata. Twopir Consulting profiles the fields your connector reads, normalises client names, matter numbers, picklists and practice codes, makes sure every value has a matching alias in iManage, and carries each fix through to the workspaces that already exist. Right values in Salesforce, right metadata in iManage.

Cleansing Model
WHERE BAD VALUES START Salesforce Fields Names · Numbers · Picklists Workspace Inputs Naming format · custom1–30 Inaccurate Incomplete Inconsistent TWOPIR CLEANSING LAYER Profile Completeness Format checks Normalise Names and codes Picklists, aliases Update & Guard Existing workspaces Validation at entry SANDBOX FIRST · ALIASES BEFORE VALUES · NO BLIND UPDATES 2πr CLEAN WORKSPACE METADATA Names Match Workspaces resolve the first time Valid Profiles custom1–30 values match iManage aliases Fixes Applied Existing workspaces updated and verified PROFILE · STANDARDISE · ENRICH · UPDATE · VERIFY · GUARD
12+
Years Salesforce delivery
500+
Clients served
250+
Deployments delivered
40+
Salesforce consultants

Trusted by 500+ organizations — including law firms and professional-services businesses that run client and matter data through Salesforce with Twopir Consulting.

Social Justice Collaborative
Bernstein Liebhard LLP
LegalZoom
Sterling Law Offices, S.C.

What We Work With

  • Salesforce Partner
  • Validation Rules
  • Picklist Value Sets
  • Salesforce Flow
  • Reports & Dashboards
  • iManage Work
  • iManage Integration for Salesforce
Where Bad Values Go

Six kinds of bad value iManage inherits

The iManage connector builds a workspace name from Salesforce merge fields and writes Salesforce values into iManage profile fields custom1 to custom30. Whatever is in those fields is what iManage gets: a wrong value becomes a wrong workspace name, an empty one becomes a gap in the profile, and an inconsistent one splits clients that should sit together. These are the six we fix most.

Inaccurate client and matter numbers

A mistyped or outdated client number in Salesforce links the record to the wrong workspace, or to none. If the numbers differ between Salesforce and the systems behind iManage, the naming format matches the wrong workspace or creates a duplicate.

Incomplete fields behind the naming format

A blank merge field leaves a gap in the workspace name, and a blank custom profile value leaves the workspace without the client, matter or practice metadata that people search and file by.

Outdated values on existing workspaces

A client renames or a matter changes type, and Salesforce is corrected. As we read the vendor documentation, names and profile values are set when a workspace is created or updated, so the existing workspace keeps the old values until something updates it.

Inconsistent picklists and practice codes

"Litigation", "Lit." and "Disputes" mean one practice to a partner and three values to a template match field. Inconsistent codes leave workspaces on the wrong template or outside the filters people rely on.

Commas that break name matching

The connector's help centre lists an unresolved known issue: workspaces with a comma in the name cannot be retrieved when records are associated by workspace name. "Smith, Jones & Co" is a normal client name and a broken link.

Values with no alias in iManage

iManage documents that each custom field takes its values from aliases, which must be added before they can be used. A Salesforce value with no matching alias, or a code written two ways, has nowhere valid to land.

Definition

iManage data cleansing, defined

iManage data cleansing is the work of correcting and standardising the Salesforce values that become iManage workspace names and profile metadata, then carrying those corrections through to the workspaces that already exist. It covers values that are inaccurate, incomplete, outdated or inconsistent in the Accounts, Contacts and client or matter records your connector is configured on, and the processes that keep them correct afterwards.

Three parties are involved. Salesforce holds the values and provides the tools to correct and guard them: validation rules, picklists, Flow and bulk updates. The iManage connector, the iManage Integration for Salesforce powered by Mitratech CaseCloud, reads those values into workspace names and custom profiles, but neither Mitratech nor iManage documents any data cleansing or profiling tooling of its own. Twopir Consulting does the cleansing on the Salesforce side, works with your iManage admin on aliases and existing workspaces, and builds the checks that stop bad values coming back.

Cleansing deals with values that are wrong. Records that exist twice are a deduplication job, which we run as a separate service. A fixed-scope assessment that ends in a findings report is a data quality audit, and the standards and ownership model that decide what "correct" means are data quality consulting.

For how the connector is set up and mapped, read our guide to iManage Salesforce integration options, setup and pitfalls.

Technical Considerations

The Salesforce values iManage depends on

Each behaviour below is documented by Mitratech or iManage. The other two columns say which Salesforce values it depends on, and what we cleanse before it runs on your data.

Connector and iManage behaviour as described in the CaseCloud Help guide to the iManage Workspace Configuration Manager and the iManage Control Center help.
Documented behaviourValues it depends onWhat we cleanse
Workspace naming formatThe workspace name is built from Salesforce merge fields, and with association by workspace name, the record finds its workspace by that name.Every field in the format: no blanks, one spelling, no stray punctuation or trailing spaces.
Custom profiles, custom1 to custom30Values map by type: lookup fields to custom1–12, custom29 and custom30; text to custom13–16; numbers to custom17–20; dates to custom21–24; booleans to custom25–28.Each Salesforce field checked against the type of the profile field it feeds, and formats made consistent.
Aliases for custom fieldsCustom field values come from aliases that must be added in iManage before use, and a resolved lookup alias must be unique throughout iManage Work.Salesforce codes reconciled with the alias list, so every value has exactly one alias to resolve to.
Parent alias for custom2 and custom30These child fields need a parent alias format, the way a matter sits under its client.Matter-to-client relationships in Salesforce checked, so each matter value has a valid parent.
Template match fieldsTemplates are filtered against workspace custom metadata, on at most two match fields, and folders can inherit custom values from their workspace.The practice, matter-type or office codes that pick the template, normalised to one value each.
Workspace names with a commaAn unresolved known issue: these workspaces cannot be retrieved when association is by workspace name. The vendor's workaround is to link by custom profile.Client names with commas identified, and those records moved to custom profile association on a clean key.
Values set on create or updateAs we read the vendor documentation, names and profile values are set when a workspace is created or updated, not synced continuously.A workspace update step after every cleansing batch, so the fix reaches iManage, not only Salesforce.
Normalisation

Normalisation rules for firm data

Normalisation decides one correct form for each value and converts everything else to it. We write the rules with the people who own the data, test them on a sample of your records, and apply them in Salesforce, where the connector reads them.

Client & Company Names

The name that becomes a workspace name has to be written one way. We set the house form and convert the variants to it.

  • Legal-entity suffixes in one form
  • Ampersands and "and" settled
  • Commas handled for name matching
  • Leading and trailing spaces removed
  • Trading names kept in a separate field

Client & Matter Numbers

Usually the strongest key in a firm, and often the messiest. One format, one source, and the same value in Salesforce as in iManage.

  • Padding, prefixes and separators fixed
  • Format checked by validation rule
  • Each matter tied to a valid client
  • Client ID and Matter ID as mapped keys
  • Numbers agreed with your system of record

Picklists & Practice Codes

Practice areas, matter types and offices often drive template choice and filtering. Each needs one controlled list that matches iManage.

  • Free-text values mapped to a picklist
  • Retired values mapped, then removed
  • Shared value sets across objects
  • Matter type codes reconciled with aliases
  • Labels kept separate from codes

Addresses & Jurisdictions

Country, state and jurisdiction values feed reporting and, in many firms, a custom profile field. We standardise them once.

  • Countries and states in one standard
  • Jurisdiction values from a set list
  • Billing and registered addresses split
  • Postal formats checked per country
  • Office values matched to your offices

Contacts & Relationships

Contact data decays as people move firms and change roles. We correct what can be verified and flag what cannot.

  • Email and phone formats checked
  • Titles and roles standardised
  • Movers flagged for review
  • Bounced emails marked, not deleted
  • Opt-outs and consent preserved

Dates, Numbers & Flags

iManage has separate custom fields for numbers, dates and booleans. A value stored as text in Salesforce needs converting before it maps.

  • Text dates converted to date fields
  • Numbers stripped of stray characters
  • Yes/no text turned into checkboxes
  • Open and close dates checked for order
  • Each field matched to its profile type
Enrichment

Filling gaps without new errors

Enrichment fills fields that are empty or stale. In a firm, the best source is rarely an outside data vendor: iManage's own Security Policy Manager documentation notes that client and matter details are typically imported from a time and billing or practice management system. We fill from the system that owns each value first, and treat outside data as a suggestion.

GapWhere the value should come from
Client and matter numbersThe billing or practice management system that issues them, never typed in by hand.
Matter type and practiceThe intake decision, recorded as a picklist value that maps to an iManage alias.
Responsible lawyer or officeThe matter's staffing in your system of record, matched to Salesforce users.
Company details and addressesVerified client correspondence first. Third-party data only as a suggestion a person approves.
Contact titles and emailsThe relationship partner or BD team, with bounces and movers flagged for them to confirm.
Fields nobody can sourceLeft blank and reported. A guessed value in a workspace name is worse than an empty one.
Cleansing Workflow

Getting fixes into existing workspaces

Correcting Salesforce is half the job. Because the connector sets names and profile values when a workspace is created or updated, a cleansed value only reaches iManage when something updates the workspace. These are the eight moves in every cleansing batch we run.

Aliases first

Your iManage admin adds or corrects the aliases the cleansed values will resolve to, before any Salesforce value changes.

Pause auto-create

Auto Create Workspace makes a workspace for any record it cannot match. During a bulk rename, that would mean new empty workspaces, so it waits.

Fix in a sandbox

Each batch of corrections runs first in a sandbox connected to iManage, and every changed record is checked against its workspace.

Bulk update in batches

Production corrections load in batches small enough to check, with the before and after value of every field kept for rollback.

Update the workspace

The connector's Auto Update Workspace Name option, its documented workspace automation or a Flow pushes the corrected name to each linked workspace.

Folders and profiles too

Folder names have their own auto-update option, and folders can inherit custom values from the workspace, so both are checked after the update.

Relink on a clean key

Where names will never be reliable, such as client names with commas, records move to custom profile association on a cleansed identifier.

Verify, then resume

Every corrected record must resolve to exactly one workspace with the right values before auto-create and the rest of the automation switch back on.

Configuration

Most of it is rules, picklists and Flow

Validation rules, controlled picklists, Flow that updates workspaces, reports that find bad values, and the connector's own settings: naming format, association method, auto-create and auto-update.

We deliver them that way, because configuration is what your admin can maintain.

Development

Code, when volume demands it

Batch corrections across a large backlog, transformation logic a bulk load cannot express, or a step that finds and updates each linked workspace through the connector's documented Apex actions.

That work uses standard Apex and the connector's published invocable methods, never changes to the managed package, which would break your upgrade path.

Ongoing Hygiene

CRM hygiene that runs after we leave

A cleansed org drifts back within months unless the same rules guard every entry point. We build the controls into Salesforce, so bad values are stopped or caught before they reach a workspace. Duplicate records follow their own prevention design in our deduplication service.

ControlWhat it catchesHow it runs
Validation rulesA client or matter number in the wrong format, or a record saved without a field the naming format needs.At every save, by users, forms, imports and integrations alike.
Controlled picklistsPractice, matter-type and office values typed freely instead of chosen from the list iManage expects.On the record page and on intake forms.
Readiness check before workspace creationA record about to create a workspace with blank, malformed or unaliased values.In the Flow that creates the workspace, before the connector is called.
Exception reportsBlank key fields, values outside the agreed lists, and names with characters that break matching.Scheduled to the data owner, weekly or monthly.
Change-triggered updatesA corrected client name or matter value that never reaches the existing workspace.A Flow that updates the linked workspace when a mapped field changes.
Import and integration checksBulk loads and system syncs bringing in values that do not match the house formats.Mapping rules agreed per source, tested before each new feed.
Use Cases

Six cleansing jobs firms bring to us

The cleansing scope changes with what triggered it. These are the situations we plan for most often, and what each one fixes.

Before the Connector Goes Live

A workspace configuration is about to be activated, and every record in the object will start finding or creating workspaces.

Bad values
Blanks and variants in the naming fields
Cleanse
Naming format fields and custom profile sources
Result
Workspaces created right the first time

Workspaces Named the Old Way

Salesforce has been corrected over the years, but the workspaces still carry the names and values they were created with.

Bad values
Outdated names and profiles in iManage
Cleanse
A workspace update run, record by record
Result
iManage agrees with Salesforce again

Client Numbers That Disagree

Salesforce and the billing system number the same clients differently, and records link to the wrong workspaces.

Bad values
Inaccurate or mixed-format numbers
Cleanse
Numbers reloaded from the system of record
Result
One shared key across both systems

New Templates or Practice Groups

The firm restructures practice groups or introduces templates matched on practice and matter type.

Bad values
Old codes and free-text practice values
Cleanse
Picklists remapped and aliases aligned
Result
Each matter lands on the right template

Names That Will Not Match

Client names with commas or special characters fail to retrieve their workspace when association is by name.

Bad values
Characters that break name matching
Cleanse
A clean identifier for custom profile association
Result
Workspaces found regardless of the name

After a Migration or Merger

Records arrive from another CRM or another firm, each with its own formats, codes and gaps.

Bad values
Foreign formats, missing fields, legacy codes
Cleanse
Mapping rules per source, then normalisation
Result
One house format before any workspace is made
Our Approach

From a field profile to values that hold

Scope depends on how many fields the connector reads, how many records and workspaces already carry bad values, and how many systems feed Salesforce. We size the work after profiling your data, not before, and agree each normalisation rule with you before a value changes.

Step 01

Map & Profile

Every Salesforce field in your naming formats and custom profiles, profiled for blanks, formats, variants and values with no alias in iManage.

DeliverableField map and value profile

Step 02

Cleansing Rules

One correct form per value, the source for each enrichment, and the conversion for every variant, agreed with your data owners and iManage admin.

DeliverableSigned-off rules and source list

Step 03

Aliases & Sandbox Run

Aliases aligned in iManage, then a representative batch cleansed in a connected sandbox, with each record checked against its workspace.

DeliverablePilot report and batch runbook

Step 04

Production Cleansing

Corrections loaded in batches, with before and after values kept, and auto-create paused while names change.

DeliverableChange log per batch

Step 05

Workspace Update

Each corrected record's workspace and folders updated, then verified: one workspace, the right name, the right profile values.

DeliverableWorkspace reconciliation report

Step 06

Guard & Handover

Validation rules, picklists, readiness checks and exception reports switched on, admins trained, or we stay on for ongoing support.

DeliverableHygiene controls, reports, admin guide

Outcomes

What changes when the values are right

Results depend on how clean your matter data is to begin with, so we profile your baseline in step one and report against it, using measures your own team can rerun.

OutcomeWhat changesHow it is measured
Consistent workspace namesWorkspaces are named one way, so people and the connector find them first time.Workspaces created from templates with consistent names.
Complete profilesClient, matter and practice metadata is present on every connected workspace.Blank rates on each mapped Salesforce field, before and after.
Documents in the right placeFewer documents filed against the wrong client or matter.iManage reports on documents filed outside the expected workspace.
A workspace on day oneNew matters pass the readiness check and get the right workspace at intake.A Salesforce report of new matters with a linked workspace.
Values that stay cleanBad values are blocked at save or caught within the reporting cycle.Validation rule blocks and exception report counts per month.
Client Outcomes

Proof from our iManage engagements

Both engagements below are Twopir iManage and Salesforce integrations rather than cleansing projects. They are here because they show what follows when Salesforce values map cleanly onto iManage workspaces. Each figure is scoped to the engagement that produced it.

TwoPir Consulting always provided us the best solution for each and every requirement. They always impress us with their results. We are very happy to work with them. For Imanage requirement they helped us to set up it easily and in effective time.
Louise Operations Executive · Law firm, custom iManage build Client ID · Matter ID · Matter Type Code Mapped
Case Study

US Law Firm — 150 Attorneys

iManage connected to Salesforce through the AppExchange connector, with direct record-to-workspace mapping.

90% Drop in misfiled or duplicate documents
85% Faster document retrieval
8 wks From kickoff to go-live
Read the iManage Case Study
Why Twopir

Cleansing by people who know both systems

Cleansing an iManage-connected org is Salesforce work with document consequences. It takes someone who knows which fields the connector reads, and what has to happen in iManage when they change.

We cleanse what the connector reads first

We start from your workspace configurations, not from every field in the org, so the effort goes where a bad value turns into a bad workspace.

We finish the job inside iManage

A fix that stops at Salesforce leaves the old values in every existing workspace. We plan the alias work and the workspace update with your iManage admin.

We stay inside documented tools

Validation rules, picklists, Flow and Salesforce bulk updates, plus the connector's documented settings and automation. Nothing that touches the managed package.

We leave controls, not just clean data

You get the rules, the reports and an admin guide. When you want us to stay, ongoing support through our legal Salesforce consulting team is a standing offer.

Common Questions

iManage data cleansing questions, answered plainly

They correct and standardise the Salesforce values that become iManage workspace names and custom profile metadata: profiling the fields your connector reads, normalising client names, client and matter numbers, picklists and practice codes, filling gaps from the system that owns each value, aligning values with iManage aliases, updating the workspaces that already exist, and adding validation and reporting so bad values do not return. Twopir Consulting does the cleansing on the Salesforce side and plans the iManage steps with your iManage admin.

Not on their own. As we read the vendor documentation, the connector sets workspace names and custom profile values when a workspace is created or updated, not through a continuous sync. After each cleansing batch we update the linked workspaces using the connector's Auto Update Workspace Name option, its documented workspace automation or a Flow, then verify that each record resolves to one workspace with the corrected values.

It is a known issue the connector's help centre lists as unresolved: workspaces with a comma in the name cannot be retrieved when records are associated by workspace name. The vendor's workaround is to link records by custom profile instead. We find the affected client names and move those records to custom profile association on a cleansed identifier such as the client number.

Yes. iManage documents that each custom field takes its values from aliases, which must be added before they can be used, and the connector's alias format resolves to an alias that must be unique throughout iManage Work. That is why we reconcile Salesforce codes with the iManage alias list and have the aliases added first, before any cleansed value is written to a custom profile.

Yes, wherever they feed a naming format, a custom profile or a template match field. Once a workspace configuration is activated, every record in that object can find or create a workspace with whatever values it holds. Normalising practice, matter-type and office codes first means workspaces start on the right template with the right metadata, instead of being corrected one by one later.

Carefully. Client and matter numbers, matter types and staffing should come from the system that owns them, usually your billing or practice management system and your intake process. Outside data can suggest company details or addresses, but we treat it as a suggestion a person approves, never let it overwrite a system-of-record value, and record where every filled value came from.

With controls inside Salesforce rather than another project. Validation rules check formats and required naming fields at every save, controlled picklists replace free text, a readiness check stops a record creating a workspace with blank or unaliased values, a Flow updates the linked workspace when a mapped field changes, and exception reports go to the data owner on a schedule.

Next Step

Find the values your workspaces get wrong

A first conversation covers which Salesforce fields your connector reads, where those values come from and which workspaces you suspect are wrong: enough to say what a cleansing project would take and where to start. No obligation to proceed.

Talk to a Salesforce architect who works with iManage