Use caseInsurance and banking

Content consolidation after a merger

Two insurers merged eighteen months ago. Their claims teams share a floor, yet taking over the other side's file still means asking for an email.

Both sources are scanned with the same measuresOne filing plan, signed by both sidesRights are mapped once and never widened

Actions on this campaign
The operations engineInventory, both companies

6.6 million documents in FileNet, 2.9 million in SharePoint, described with the same measures. 18,240 policy numbers exist on both sides.

source · discovery scans, both sources
The verdict on the batch

Some documents need a person · each one is named, per source

01

The friction

In two paragraphs

The volume is manageable. What slows everyone down is that the two companies never filed the same way: different classes, different folder logic, policy numbers that overlap, security groups in two directories. Copy both into one repository as they are, and you get two filing plans under one roof.

Decisions come before any document moves. Both sources are scanned with the same measures, the business signs one filing plan, each source gets its own mapping onto it, and the colliding numbers get a rule. Then the content moves, one line of business at a time.

Two filing logicsOperations engine
Same claim, two vocabularies. And the same eight-digit number can point to two different customers.
Search: 40118827Repository
One number, both policies. Each is filed the same way, under its own group key.

The work runs in a fixed order, and skipping a step costs a file: measure both sides the same way, agree one plan, settle rights and numbers, then move and reconcile each source on its own. Ellen and Stefan start with the plan, Rania settles the rights, and Lucas ends up opening a claim from the other company.

02

One filing plan

Both sources are scanned first, then the two filing logics are laid side by side and merged into one plan.

Step 1Discovery

Scan both sources with the same measures

Ellen Brody, the group content architect, points the operations engine at the FileNet object store of Arvelle and at the SharePoint sites of Corbin. The same scan runs on both, and nothing moves.

Classes and content typesProperties and columnsFoldersVersionsRights
Inventory, group consolidationOperations engine
Two systems, one set of measures, one list to work from.
Both sides speak the same languageThe workshops start from one list of facts, instead of two teams describing their own system.
Step 2Filing plan

Merge the two filing logics into one plan

Stefan Kowalski, the records manager, runs three workshops with the claims and policy managers of both companies. The shared plan files by line of business, then by policy, then by claim.

Where the two sides named the same thing differently, the workshop picks one name and records the old ones as aliases. Each ruling goes into a decision log.

Shared filing plan v3Repository
The plan is the target structure. Both sources are restructured onto it on the way through.
The business signs the structureAdjusters from both sides will find a claim where they expect it, because they chose where it goes.
Step 3Mapping

Map each source onto the shared classes

Each source gets its own mapping onto the same target classes. FileNet properties map one to one in most cases. SharePoint needs more rules: the claim number sits in a column on some libraries and only in the folder name on others.

Ellen writes a rule that reads the folder name when the column is empty.

Mapping, SharePoint claimsOperations engine
Two mappings, one target. Each rule is versioned.
Each side keeps its own logic until the moveThe rules absorb the differences once, in the pipeline. Nobody refiles by hand afterward.
03

Rights and numbers

Two directories, two security models, two numbering schemes. Each could expose or lose a file, so all three are settled before the pilot.

Step 4Rights

Map two sets of groups onto shared roles

Rania Mansour, the identity and access administrator, takes the groups that grant access in each source: FileNet rights on classes and folders, SharePoint permission groups on sites and libraries. She maps both onto the shared roles of the repository.

The inventory also listed the folders whose rights differ from what they inherit. Each one is mapped explicitly.

Rights mappingOperations engine
Restricted stays restricted. Bodily injury files map to a restricted role on both sides.
Eighteen months after the merger, who decided which of the two companies' staff may read a bodily injury file, and where is that written?
Rights are mapped once, never widenedA group that opened files to almost everyone stays unmapped. Its files wait until someone decides who should read them.
Step 5Data quality

Settle the policy numbers that exist twice

Both companies numbered policies with eight digits, and 18,240 numbers exist on both sides for different customers. Stefan and the policy teams agree on a rule: a group policy key made of the entity code and the old number.

The old number stays as a searchable property, so adjusters can still type the number a customer gives on the phone.

Number collisionsOperations engine
Same number, different customers. The group key keeps each one unique.
No file lands on the wrong customerA colliding number never merges two policies. The rule is applied in the pipeline, on every document.
Step 6Pilot

Run the pilot on one line of business, both sources

Ellen runs the pilot on the 2023 auto claims, both companies in the same batch. Each source is extracted through its own connector, transformed with its own mapping and loaded into the same staging space.

The counts are shown per source, so a problem on one side does not hide in the total.

Pilot, auto claims 2023Operations engine
The 752 exceptions are SharePoint files with no claim number in the column or the folder.
Two sources, one batch, two sets of countsThe team sees which side caused each exception, and the right team fixes it.
04

One repository

The pilot is reconciled per source, an adjuster tries it on real files, and the remaining lines move in waves.

Step 7Reconciliation

Reconcile each source on its own

The reconciliation report has one part per source. Each document has its own line, with its FileNet or SharePoint identifier next to the new one. Ellen shares each part with the former IT team that knows that data best.

Reconciliation, pilotOperations engine
The report exports as it is, one part per source.
Each IT team checks its own sideThe people who knew the old systems confirm what left them. The proof does not rest on one person.
Step 8Exceptions

Give the 752 files their claim number

The Corbin claims team gets the list of 752 files. For most of them an adjuster knows the claim from the letter itself, and fills in the number in the list. The failed objects are reprocessed with that value, without rerunning the pilot.

689 numbered by an adjuster63 kept as unfiled correspondence
The people who know the claim decideNo guess is made on a missing number. Each file is placed by someone who can tell, or kept aside with a reason.
Step 9Search

An adjuster finds a file from the other company

Lucas Ferreira used to work at Arvelle. He takes over claim CLM-23-008112, opened at Corbin. He types the old policy number he was given on the phone, gets both policies that carry it, and opens the Corbin one.

Its adjuster report sits in the claim folder, filed the same way as his own.

Search: 40118827Repository
Search respects the rights of whoever runs it. Lucas sees what his role allows.
Nobody emails documents across the floorThe file from the other company opens where the plan says, with the number the customer knows.
Step 10Waves

Move the remaining lines in waves

With the pilot signed, Ellen and Stefan plan the remaining lines: homeowners, health, then policy contracts and archives. Each wave reuses the mappings, the group key rule and the rights mapping, and gets its report per source.

The two old systems go read-only line by line, as their content is signed.

Consolidation planOperations engine
Each wave waits for the signature of the one before.
The merger ends one line at a timeEach team switches when its own content is signed, and the rest keep working as before.
05

What comes out

A batch is judged twice, once per source, and lands in one of three states. The state decides whether the next line of business moves.

Reconciled

Both sources match

Every document is filed under the shared plan, with rights no wider than in its source.

After that: the wave is signed and the source goes read-only for that line.
Exceptions listed

Some documents need a person

A missing claim number, an unmapped group. Each one is named, with the source it came from.

After that: the team that knows that source fixes it, and only those documents run again.
Batch held

A control fails on one source

The counts do not agree, or a rule filed many documents in the wrong place.

After that: the next wave waits until the cause is found and a person decides.
What the operations engine does not decide

It does not choose the filing plan, the group key or who may read a bodily injury file. Across the ten steps on this page, every one of those choices is made by the group's team, logged and signed.

The engine scans, applies each source's mapping and reports per source. The control is in the decisions made before the pilot, so it holds for nine million documents.

06

In numbers

Drawn from the Arvelle and Corbin consolidation. Two other companies, with other sources and another plan, will draw their own.

1 filing planfor both companies, signed in three workshops and applied to every document.
0 documentsloaded with wider rights than they had in their source.
18,240 numberskept unique by one rule, with the old number still searchable.

Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.

Three principles behind the figures

Same measures on both sidesDiscoveryBoth sources are scanned the same way, so the workshops start from one set of facts.
Decide before movingFiling plan and rightsPlan, rights and numbering rules are settled and logged before the pilot.
Prove per sourceReconciliationEach source has its own counts and its own report, read by the team that knows it.
07

Who it is for

Two companies share one repository only when IT, records and access management agree. Each of them signs for something different:

IT and architecture

Group CIOs and architects

The merger is signed, and two platforms still run side by side with their own costs.

  • FileNet, SharePoint, Documentum or OpenText, scanned the same way.
  • Each source keeps its own connector and its own mapping.
  • Waves follow your lines of business.
  • The target runs in your data center or in the cloud.
Records and compliance

Records managers

Two filing logics, two retention habits, and your signature on both.

  • One filing plan, agreed with both business sides.
  • Old names kept as aliases, every decision logged.
  • Retention and filing rules travel with the content.
  • Each wave has its own report, filed.
Identity and access

Access administrators

Two directories, where one mistake opens files to the wrong company.

  • Groups of both directories map onto shared roles.
  • Folders with their own rights are listed by the scan.
  • Unmapped groups hold their documents back.
  • Restricted content stays restricted on both sides.

Your first move

With one line of business. Scan both sources, run the first workshop on its filing plan and pilot it, while every other line stays where it is.

Both old systems keep running until their content is signed, so the teams work as usual while the plan is built.

Let's talk

Lay your two filing plans side by side

Send us the class list and the folder logic of each entity. We will scan both with the same measures and prepare the first workshop on a shared plan.

The screens on this page are drawn to show one step at a time, with example data.

Uxopian Software helps organizations put AI to work across the systems they already run, without giving up control of their data, their infrastructure or their critical processes.