Many existing FileNet customers have started their journey to modernize existing traditional on-premise FileNet environment to a container platform like Red Hat OpenShift. There are many benefits of moving to a container platform such as fast deployments, portability, scalability and elasticity. Many have similar questions as they start drafting a migration plan. In this blog series, we will answer common questions around migrating to FileNet containers. Here, we will cover migration strategies and important considerations for initial planning.

At a high level, there are three core container migration strategies:

1. Direct migration
2. Parallel environments (aka side-by-side)
3. Disconnected/partial migration

There are pros and cons for each, and things you should take into consideration that will impact your decision.

• What is the timeline and schedule to complete the migration?
• What version of FileNet software are you currently on?
• How many custom applications and/or solutions that need or can migrate?
• What other IBM products are integrated into this FileNet environment?
• Are you migrating to containers on-premise or public cloud?

For example, let’s focus on timeline and schedule. If you have a short runway to complete the migration to container platform, and your environment is relatively small and simple (no complex integration or custom applications/solutions) then direction migration is a good option. Alternatively, if you are on an older version of FileNet prior to container support, then the parallel environment option is not possible since it requires both environments to be the same FileNet version. You would need to upgrade your existing FileNet environment to at least 5.5.1 which will impact the timeline and schedule requirements. Depending on your existing FileNet deployment, there may be other things to take into consideration that will eventually become requirements for the migration.