When it comes to finding, editing or sharing documents in Microsoft 365, SharePoint Online can easily replace IBM FileNet Content Manager. However, things get a lot more difficult when you’re dealing with documents that other systems act on. Let’s say you’re approving credit in FileNet. That approval means a loan will need to be processed. You could do that in SharePoint, but only if the lending system receives the right approval, for the right version, from the right authorized user.
Rather than deciding to move everything to SharePoint, look at what your team needs per document class. Working documents might be best at home in SharePoint, while FileNet could be the best place to store signed agreements. And you may find that you don’t need to hold on to that outdated correspondence at all. To complicate matters even more, documents within the same file can have different owners and serve different purposes.
So how do you know whether a particular collection would be better off in SharePoint? The best way to test this is by choosing a collection with a clear owner and recognizable daily task. First, let two policy editors collaborate on revising an existing draft. Once the revision is done, ask a different branch employee to retrieve the current policy. If both tasks are easily done using their regular accounts, you’ll know the content is suitable to move from FileNet to SharePoint.
Let's say you’re using an illustrative FileNet document class called Credit Approval Memo. Each memo within that class has a specific loan ID, a borrower name, a review status and an assigned underwriter. The memo is prepared by a lending assistant, approved by a credit officer, and recorded by the loan application. Within that overall process, there are four distinct parts that have different handling requirements.
Document class and metadata. Pick a SharePoint content type to represent the memo with columns for its properties, then decide which system owns each value. If the load ID is assigned by a loan application, avoid manual re-entry. Instead, test with an actual ID that includes leading zeroes. Can a user find the memo by its ID and distinguish it from earlier memos by the same borrower? If staff usually open the whole dossier, a SharePoint document set can group related documents. See the Microsoft documentation on document sets for more details.
Access rights. Sometimes, a loan team may need access to the dossier, but internal assessment is restricted to the credit committee. First, decide who should own the assessment and who should remain on the committee. Once that’s settled, give the same direct link to a committee member, a loan officer and someone who was recently removed from the committee. Test what each person can access to ensure everything works as intended. In this case, a quick library view alone will not be enough!
Approval and exceptions. Let’s say a specific memo must be approved by an authorized officer, and the lending system must receive their decision. If you’re working in a SharePoint-based design, you could use Power Automate for approval and add a separate integration to update the loan. Ask the authorized officer to reject a memo, approve a revision and then simulate a failed update. Can the right people see that the loan is still pending? And can they retry the update without requesting a second approval? Keep this document class in FileNet until the process owner can answer both questions affirmatively.
Closed records. If retention starts when a loan closes, the SharePoint upload date is not the right starting point. Microsoft Purview supports event-based retention, linking a business event to labeled content. Ask the records owner to trace a closed loan from its recorded closure date to the agreements covered by the rule. Include a loan on hold, and verify the outcome before approving the design. See Microsoft guidance on event-based retention for more information.
Community Preservation Corporation moved its loan documents from FileNet to SharePoint Online. In the new environment, employees could easily browse folders or search for specific content. The source repository proved something of a challenge: some FileNet entries had no physical file attached, and older metadata wasn’t consistently formatted.
Details like those can make or break a content migration. For example, if a SharePoint search returns nine agreements while FileNet lists ten entries, that could simply be a transfer error. Alternatively, it could very well be that one of the entries never had a file to begin with. When testing, be sure to include a known exception in your evaluation and ask the loan team for input. For someone reviewing a loan, a documented explanation for the tenth entry may be as important as the nine agreements they can open.
Want to find out more? Read Xillio’s Community Preservation Corporation case study.
Replace FileNet when business owners can complete their work in SharePoint and account for the records left behind. Before retiring FileNet, ask application owners to identify any processes that still read or write FileNet object IDs. For example, an overnight job that retrieves signed agreements may still depend on the repository even after employees stop opening it.
Keep FileNet for any document class where controls or integrations remain essential. Document the reason and assign an owner. A specific dependency—such as “the servicing application retrieves the signed agreement by FileNet ID”—gives a future project something concrete to investigate and cost.
Use both platforms when there is a clear handoff. For example, a team might use SharePoint Online to draft a memo, but store the signed version in FileNet. Define which copy should be used for an audit request, how colleagues find it and what happens if filing fails. Make sure to factor in the operating costs when comparing your options.
Make sure to test with both a common document class and one that's a little more difficult. Have the people involved show every step in the process, from drafting and approving to publishing and retrieving. Once you know which document classes belong in SharePoint Online, define the migration scope and agree how to verify the results.
Explore Xillio’s approach to IBM FileNet to SharePoint Online migration.