Integrating knowledge bases and client data after a consulting acquisition

Why consulting integrations are different#

Consulting firm acquisition integration is different because the firm's knowledge and its clients' information sit in the same folders. A proposal template, a client's cost model and a partner's review notes may share one SharePoint site, and the acquired firm's consultants have been copying slides between engagements for years.

Platform owners usually want the combined firm to reuse acquired methodologies quickly, and that goal is sound. The order matters, though. A shared knowledge base that absorbs client deliverables can breach confidentiality obligations the acquired firm accepted, and those obligations generally survive the deal.

Professional services platforms also inherit people risk. Consultants keep working files in personal folders, email and local drives, and a systems inventory only finds what was stored centrally. Ask each practice lead where their team actually keeps working files before treating the inventory as complete.

What the acquired firm holds, and who usually owns it#

The acquired firm's records fall into a handful of types with different typical owners. Ownership is set by each engagement letter, MSA and statement of work, so treat this table as a starting assumption to test, not as the answer.

The integration sequence, stage by stage#

The integration sequence runs in five stages, and each stage ends with a document someone signs off. Skipping the rights stage is the most common shortcut and the hardest to reverse, because once content has been copied into templates it is difficult to trace.

Permissions deserve their own design session. Smaller firms often granted broad internal access because everyone worked across engagements, while the platform may run stricter walls. Map the acquired firm's groups onto the platform's model rather than copying them, and keep a log of who could see each client folder before and after the move.

Run the sequence firm by firm when the platform has made several acquisitions. Each source firm signed different contracts, and a combined review blurs which terms apply to which folder.

• 1Inventory: list every repository, site and system at the source firm, with its owner, the years it covers and the clients it represents.
• 2Rights check per source firm: read the firm's MSA templates, signed engagement letters, NDAs and client-specific restrictions, and record which folders each governs.
• 3Permissions: design access around client walls and conflicts, so client folders stay limited to the original team and designated reviewers.
• 4Migrate: move firm-owned knowledge into the platform's knowledge base, stripping client names and figures from reusable templates.
• 5Archive: keep client files in a restricted archive under their original terms, with a retention schedule and a named custodian.

The rights caveat for acquired client files#

Acquired client files remain bound by the confidentiality and ownership terms the acquired firm signed. Some client agreements restrict use of client information to the engagement, some assign deliverable ownership to the client, and some require return or destruction when the work ends. A change of ownership at the consulting firm does not usually loosen those terms.

Some agreements also limit assignment or require notice on a change of control. Ask counsel to confirm how the deal structure, whether an asset purchase or a stock purchase, affects which contracts and files moved, and whether any clients must be notified.

The working rule: firm-owned knowledge can be migrated and reused once client details are removed; client files stay archived and walled unless the client agrees otherwise.

Combining CRMs without creating conflicts#

Combining CRMs after a consulting acquisition is a conflicts exercise as much as a data cleanup. When two firms' client lists merge, the platform may find that it now advises direct competitors, or that the acquired firm's pipeline includes a prospect the platform is pitching against.

Keep the source firm tagged on every migrated account and opportunity. Win-loss notes and proposal outcomes are among the most useful records a consulting firm holds, and the tag preserves which firm's methods and pricing produced them.

Illustrative: an operations advisory platform adds a supply-chain boutique#

Illustrative: a fictional operations consulting platform acquires a supply-chain advisory boutique. The boutique stores its work in one SharePoint tenant and a Box account, runs an older Salesforce org, and keeps its methodology as slide libraries and spreadsheet models.

The inventory shows client folders holding network models and supplier pricing under MSAs that restrict use to each engagement. The methodology library, proposal archive and internal project reviews are firm-owned but full of client names. The platform migrates the methodology and a cleaned proposal library, walls the client folders in a restricted archive with the original engagement leads as custodians, and runs a conflicts review before merging the Salesforce org.

The combined firm starts using the boutique's methods during integration, and no client's files are exposed to consultants outside the original team.

Where licensing fits later#

Firm-owned knowledge is also what AI developers sometimes ask about: proposal-to-outcome histories, internal project reviews and playbooks that show how experienced consultants reason through a problem. Client deliverables are usually carved out.

In the SourceX five-step transaction, the Rights step reviews each source firm's contracts separately, and the Preparation step removes client, personal and confidential details before the firm approves anything. A clean integration, with firm-owned and client material already separated, makes that review far simpler.