Migrations like this rarely go as planned. Livelink and SharePoint handle content very differently, and without the right tools, it’s easy to lose metadata, break links, or disrupt teams that rely on that content every day.
In fact, based on years of field experience, Tzunami has observed that up to 60% of ECM migrations face rework or failure, usually because critical details were overlooked or the wrong tools were used.
Why Is Livelink to SharePoint Migration So Difficult?
Livelink (now part of OpenText Content Server) has been in use for decades, and in many organizations, it’s been heavily customized over time. That includes:
- Unique content classes and object types
- Custom metadata fields
- Embedded references and cross-linked documents
- Deep, sometimes inconsistent folder hierarchies
- Complex permission structures
Migrating this type of environment to SharePoint, which follows a different architecture and content model, requires more than just moving files.
Without proper planning and tooling, organizations often encounter:
- Metadata that doesn’t transfer correctly
- Broken internal links between documents
- Permissions that don’t match the intended access controls
- Incomplete version histories
- Confusion for end users who can’t find what they need
In these cases, the migration might appear complete on the surface, but critical gaps emerge once users begin working in the new system.
The Solution: A Step-by-Step Livelink to SharePoint Migration Framework
Tzunami has developed a proven approach to enterprise-grade SharePoint migration, specifically for platforms like Livelink. Below is the structured method we recommend and enable with our Deployer platform.
Pre-Migration Discovery & Analysis
- Inventory your Livelink repositories
- Analyze content types, metadata schemas, and custom fields
- Identify content to exclude (ROT: redundant, obsolete, trivial)
- Simulate the SharePoint migration using Tzunami’s preview tools
- Plan metadata mapping rules
📌 Tip: Use Tzunami Deployer’s pre-migration analysis tool to identify potential risks before the first move.
Configure Mappings and Create a Pilot Batch
- Map Livelink metadata to SharePoint content types
- Set permissions and access rules for SharePoint
- Migrate a test batch to validate version history, field mapping, and links
- Gather feedback from real users
Execute Bulk Migration
- Run the first pass using Tzunami’s Livelink Exporter + SharePoint Deployer
- Migrate documents, folders, metadata, permissions, and versions
- Transform embedded Livelink URLs into new SharePoint URLs (link rewriting)
Delta Migration Passes
- After bulk migration, run incremental/delta migrations to sync changes made during the process
- Only new or modified content is migrated, which reduces downtime and catches last-minute edits
Why this matters: In long migrations, users keep working. Without delta migration, you risk data drift. Tzunami Deployer supports full delta capabilities.
Validation and Cutover
- Run integrity checks: verify metadata, permissions, document counts
- Enable parallel user access if needed during transition
- Final cutover: shift primary usage to SharePoint, archive Livelink
Request a free consultation here and get expert insight.
Before & After: What a Clean Migration Looks Like
Let’s visualize the impact of doing it right vs doing it wrong.
| Feature / Metric | Before (Manual or Scripted Migration) | After (With Tzunami Deployer) |
| Metadata mapping | Inconsistent or lost | Fully preserved and mapped |
| Permissions | Misapplied or defaulted | Mapped accurately from Livelink |
| Version history | Often lost | Maintained through Deployer |
| Links | Broken references | Rewritten to new SharePoint URLs |
| User access | Downtime required | Delta pass enables seamless switchover |
Industry Trends: Why This Move Is Smart Now
The Enterprise Content Management (ECM) market is experiencing a massive transformation. Here’s a verified Stat:
According to Mordor Intelligence, the ECM market is expected to grow from USD 69.72 billion in 2025 to USD 145.51 billion by 2030, at a CAGR of 15.85%.
This growth reflects the shift from legacy systems like Livelink to modern platforms like Microsoft SharePoint, Teams, and Office 365.
Common Mistakes That Lead to Migration Failure (And How to Avoid Them)
Mistake: “Lift and Shift” Without Metadata Planning
Why it fails: You move documents, but lose context fields that are blank or mismatched in SharePoint.
Fix: Use Tzunami Deployer to map metadata explicitly. This includes custom fields, content types, and system metadata like authorship and dates.
Mistake: Forgetting About Embedded Links
Why it fails: Documents that reference other documents (common in Livelink) will point to nowhere.
Fix: Enable automatic link rewriting. Tzunami supports this, transforming legacy URLs into SharePoint-friendly equivalents.
Mistake: No Plan for Delta Migration
Why it fails: Users keep working during migration — and those changes get lost.
Fix: Build in incremental/delta migration using Tzunami. Run deltas after your bulk migration to ensure nothing slips through.
Final Outcome: What Does Success Look Like?
Organizations that use Tzunami’s migration framework typically experience:
- Metadata preservation (no manual fixes post-migration)
- Minimal business downtime
- No broken links or lost permissions
- Lower overhead during and after the migration
Final Takeaway
Livelink to SharePoint migration doesn’t have to be risky, messy, or time-consuming.
With the right tool like Tzunami Deployer and a strategy that includes metadata mapping, link rewriting, delta sync, and validation, you can move confidently and completely.
FAQ:
Can we preserve Livelink version history in SharePoint?
Yes, Tzunami Deployer supports full version retention.
How do we map custom metadata from Livelink?
Tzunami lets you configure mapping profiles during the export process, aligned to your SharePoint content types.
Do we need to freeze Livelink during migration?
Not necessarily. With delta passes, you can keep the source system active and sync changes after initial migration.
What about regulatory compliance (e.g., audit logs)?
All document history, versioning, and metadata are preserved, supporting compliance in SharePoint.
