Reduce platform cost
End duplicate EDRMS licence and infrastructure spend once SharePoint Online is the system of record, with a decommission plan named early, not as a surprise change request.
HP Records Manager.SharePoint, done properly.
Move records from HP Records Manager / TRIM / OpenText Content Manager into SharePoint Online. Evaluation first, architecture that respects platform limits, migration executed with care.
Evaluation before a single file moves. Design for SharePoint Online limits you cannot raise. Pilot, then gated waves with staged fees. Trustholm operates the suite. Your IM and ICT own records decisions and UAT.
EvalBefore a single file moves
5,000List view threshold we design for
PilotThen gated waves and staged fees
Consulting-operated · Australia · migrate.trustholm.com
Why modernise now
Leave expensive TRIM infrastructure without losing records discipline
Agencies still on TRIM or Content Manager face licence cost, ageing on-prem stacks, and a Microsoft 365 workplace that staff already live in. Migration is not optional forever, but a bad cutover is optional.
Work where people already are
Records that land in Microsoft 365 are searchable beside Teams and Outlook. No second login for day-to-day findability.
Keep compliance defensible
Provenance columns, retention mapping to Purview labels where in scope, and audit packs so IM can answer "where did this record come from?" after go-live.
Design for SharePoint, not a TRIM clone
Capacity is generous; unfiltered views are not. We brief the 5,000-item list view threshold before bulk load so Day 1 is usable.
Migration scope
What we move, and where it lands
Trustholm Migrate engagements cover the TRIM lineage into Microsoft 365. Hybrid "keep Content Manager forever" integrations are a different buy; we help you decide which path fits.
Source systems
- HP TRIM / Tower TRIM
- HP Records Manager
- OpenText / Micro Focus Content Manager
- TRIM Context web estates
- Workgroup and SQL-backed electronic stores
Target platforms
- SharePoint Online document libraries
- Hub and site topology for records
- Microsoft Purview retention labels (scoped)
- Search-first findability with filtered views
- Optional Teams-adjacent collaboration spaces
Why TRIM migrations fail
TRIM is a records fortress. SharePoint is a different animal
Competitors sell speed. We sell honesty about the hard parts, then design around them.
Classification vs taxonomy
TRIM hierarchies are deep and rules-based. SharePoint prefers flatter metadata. Blind folder clones blow path limits and bury findability.
Record types and custom fields
Years of custom record types need content types, columns, and views, not a single "Documents" dump.
Disposal and retention
TRIM disposal schedules sit on records. SharePoint uses labels and Purview policies. Mapping must be decided before ingest.
Record-level security
Per-record ACLs do not scale in SharePoint Online. Unique permissions ceilings force an early group-based redesign.
List view threshold
A library can hold ~30 million items. A view that tries to process more than 5,000 at once fails. Default views need selective filters.
Legacy versions and stores
Older TRIM/CM SQL and document stores need discovery, path safety, and dry-run before live waves.
Most TRIM to SharePoint pages promise "metadata intact." Few lead with the list view threshold, path length limits, and unique-permission ceilings. Trustholm walks IM and ICT through those constraints in evaluation, so go-live is operable, not just loaded.
Migrate
Consulting-operated platform, not a DIY installer
Our consultants run a purpose-built suite: pre-flight, dry-run, checkpointed live migration, and audit packs. Your IM and ICT teams own records decisions and UAT, not tooling theatre.
Pre-flight and path safety
List view threshold checks, provenance mapping, auth validation, and path-length guards before live load.
Dry-run to checkpoints
Controlled pilot of one record family, then batched waves with retries, cancel, and restartable progress.
Audit packs
CSV, Markdown, HTML, and ZIP evidence packs ready for IM leads and assurance reviewers.
SharePoint records pack
Built-in columns and threshold-safe views deployable to your records libraries.
Consultation checklist
Labelling, information architecture, permissions, search, capture, and decommission scoped in evaluation, not buried mid-wave.
Staged commercial model
Pilot exit criteria and partial payments tied to delivery gates so the agency proves the pattern before estate spend.
Engagement path
Evaluate. Design. Pilot. Scale. Support.
Evaluation
Workshops, volume model, risk register, frank SharePoint limits briefing, written findings.
Architecture
Site topology, library map, field mapping, security groups, views under the 5,000-item threshold.
Pilot
One agreed record family. Dry-run, live, champion coaching, then go, revise, or stop before estate spend.
Waves and hypercare
Gated cutovers with acceptance, then floor support, runbooks, optional retainer.
Consultation scope
Beyond bulk load, what evaluation usually covers
Tick these in workshops. Core topics are usually in; add-ons are priced as statement-of-work lines; deferred items are named early so they are not surprise change requests.
Usually in evaluation
- Purview labelling and retention
- Information architecture
- Views and provenance columns
- Permissions redesign
- Search and findability
- Training and change
Often separate SoW lines
- Email / capture continuity
- Scanning pathways
- Case / container emulation
- Legal holds
- Reporting and audit packs
- Line-of-business deep-link remaps
Name early
- TRIM / CM decommission
- Destroyed / sentenced scope
- Residency and guest constraints
- On-prem / hybrid SharePoint
Expectation setting
SharePoint has room. Views do not show everything at once.
A library can hold up to 30 million items. A view that tries to process more than 5,000 at once hits the list view threshold. We design for that before migration, so go-live is usable.
30,000,000
Max items or files in a list or library
5,000
List view threshold in SharePoint Online (not raisable)
400
Max characters in a decoded file path + name
~5,000
Recommended unique permissions ceiling
Proof
A well-trodden path for Australian public records
Moving from HP TRIM into SharePoint on Microsoft 365 is an established migration class. Trustholm brings current engineering and a consulting method that starts with evaluation, not a weekend data dump.
Evaluation-led
Limits briefing and information-architecture options before anyone migrates a record family.
Provenance kept
TRIM number and URI columns so staff and support still recognise the record.
Change that sticks
Champions, runbooks, and hypercare. Findability over a pixel clone of TRIM.
Torres Strait Regional Authority
TSRA moved from HP TRIM to SharePoint in Office 365. We use that journey, at a high level, to show agencies that this transition is achievable with the right architecture and hand-holding. Public narrative stays outcome-focused. Detailed metrics are shared in proposals where release terms allow.
Pair with ShareSight
Migrate moves and validates content. ShareSight proves who can see what on sites, personal drives, and mailboxes, before records land, during hypercare, or as a standalone estate health review.
Explore ShareSightBook a fixed-fee evaluation conversation
Whether TRIM is still your system of record or Content Manager is showing its age, start with evaluation. We will tell you what SharePoint can sustain, and what it cannot, before anyone migrates a record.
Frequently asked questions
- Can you preserve TRIM classification in SharePoint?
We map classification into metadata, content types, and filtered views, not a deep folder clone. Deep trees break the path limit and findability. Pattern choice (hub libraries, divisional sites, case emulation) is decided in evaluation.
- What happens to record-level security?
Per-record TRIM ACLs do not scale in SharePoint Online. We redesign to group-based access at library, folder, or Document Set level, document unique-permission ceilings, and call out exceptions early.
- Will it look exactly like TRIM?
No. It will work like Microsoft 365, with familiar numbers and metadata. Staff find records via search and curated views, not a TRIM UI replica.
- Can we migrate department by department?
Yes. Pilot one record family, then waves by record type, business unit, status, or year, each with scope lock, dry-run, live import, and acceptance before the next wave.
- How do disposal schedules work after migration?
We map disposal authorities into Microsoft Purview retention labels where in scope. Label IDs and authority mapping are engagement-configured, not assumed from a default template.
- Can our ICT run the tool alone?
No. Trustholm consultants operate the Migrate suite. Your team owns records decisions, UAT, and business acceptance. We are not selling a DIY agency installer.
- Should we keep Content Manager and only integrate SharePoint?
Sometimes. Hybrid CM + SharePoint integrations are a different engagement class. If Microsoft 365 is the strategic system of record, full migrate is usually cleaner. Evaluation names which path fits.
- What about the 5,000 list view threshold?
It is not raisable in SharePoint Online. Every default view we ship uses a selective filter (year, status, record type, business unit). "Show all" is not the operating model.