Supplementary services

Maintenance Services

Tailored maintenance services for systems based on IBM’s ECM product family

We believe that professional maintenance and support is the right way to reduce the total ownership costs for a software system. Maintenance also ensures useful improvements and optimization steps.

We keep systems up and running without unnecessary breaks. This is achieved with careful planning and robust implementation combined with preventive actions.

A bird's nest in a forest symbolizes Elinar's maintenance services

Migration Services

Migrate your content with speed, ease, and confidence.

We offer services that allow customers to migrate data from an old content repository to a new one quickly and easily. Elinar will handle everything from requirements specification to final delivery testing using our proven processes and tools. We always deliver migration as a service due to the customer-specific nature of content and data migrations.

Migratory birds symbolize Elinar's migration services

Migrations can be categorized into three main categories:

  1. Content-to-content migration: Content is migrated from an existing content repository to a new one.
  2. Legacy data to content archive migration: A legacy database application is being decommissioned but contains critical business data.
  3. IBM Document Manager migration: We have a long history of working with IBM Document Manager, and we are one of the few partners who can perform efficient migration to the Content Navigator platform.
1. Content repository to content

Repository migration – Elinar tools allow content migration from the following repositories:

  • IBMContent Manager, Enterprise Edition (CM8)
  • IBMContent Manager (P8)
  • IBMLotus Notes
  • IBMContent Manager OnDemand
  • IBMQuickr (both Java and Domino versions)
  • IBMConnections
  • Microsoft SharePoint
  • CIMS-compatible repositories
  • Legacy archives like Mobius, Control-D and MultiArchive
  • IBM Content Integrator-supported repositories
  • Any other content source can be supported, but may require the development of an easy-to-write connector module

We can process any supported archive, apply system and user mapping as needed. We also use optional content classification or content analytics to obtain new or changed metadata. And at the end, we store the content in the new repository.

Target Repositories – We can migrate content to the following repositories:

  • Content Manager, Enterprise Edition (CM8)
  • IBMContent Manager (P8)
  • IBMContent Manager OnDemand
  • IBMConnections
  • Microsoft SharePoint
  • CIMS-compatible repositories
  • IBMContent Integrator-supported repositories

Obtaining a content migration service

The services are available globally. Migration tools are not sold separately; we can offer the most cost-efficient way to migrate data by providing a productized service. Our pricing structure is as follows: A one-time fee for the migration tool + migration services work = hassle-free, cost-efficient migration.

Download

2. Legacy to content migration

Legacy databases contain business-critical information that must be retained for a long time. Owning and maintaining legacy databases can cause significant expenses.

Our service allows the archiving of virtually any legacy database (we do also Cobol) into IBM Content Manager. Migrating data from legacy systems allows the safe decommissioning of the servers as data is converted into documents and stored into the IBM ECM repository for long-term archiving and storage. By moving legacy data to the IBM ECM -based repository it is possible to give users a significantly enhanced user experience and usability using IBM Content Navigator.

The procedure to migrate a legacy database is straightforward:

  • Identify valuable data in the database
  • Develop mapping from the data-> meaningful business entities to be archived
  • Develop a presentation for the archive data (=document templates)
  • Map the data using Elinar’s migration tool
  • Run the conversion
  • Configure user access using IBM Content Navigator
  • Test
3. IBM Document Manager migration

We can migrate Document Manager solutions into IBM Content Navigator or Case Manager.

We have a long history of working with IBM Document Manager (DM). This allows us to migrate customer environments into a more modern browser-based user experience provided by IBM Content Navigator.

A migration project

A typical migration project involves the following steps:

  • Analyze the current DM solution
  • Perform a gap analysis on current and new functionality
  • Develop a plan to fill the gaps using Navigator plugins and other software
  • Develop a new solution design on Content Navigator or Case Manager
  • Migrate data using Elinar’s migration tool
  • Test & deploy new solution
  • Re-energize the solution by enabling new capabilities available on a modern platform.