Use casePlatform replacement
A service center works in FileNet six days a week. The last upgrade cost a weekend and two weeks of backlog. This time, agents must not notice.
Both platforms run side by side for weeksThe cutover is rehearsed with a stopwatchA person makes the go or no-go call
8.04 million documents loaded and checked while the agents work. Fewer workers by day, more at night, so FileNet stays responsive.
source · supervision, bulk loadBoth platforms agree · the lead can call go
The director of customer service set one condition: the agents must not notice the move. Eleven million documents cannot be copied in one weekend, and a platform used six days a week cannot be stopped for longer. A big-bang cutover is ruled out before it is planned.
For weeks, both platforms run side by side. The bulk load fills the new repository in the background, sync runs carry over the changes made in FileNet, and the switch only has to carry the last few hours. The cutover window is measured before it is booked.
Read the plan as four promises, kept in order: load in the background, keep the gap small, rehearse the switch, and freeze writes only for the time the last sync needs. Grace's team spends eight weeks on the first three and one Saturday evening on the last.
FileNet stays the system of record until cutover, while the new repository fills in the background.
Grace Okafor, the migration lead, writes the coexistence plan for eight weeks. FileNet remains the only place the customer service application writes to. The operations engine copies into the new repository and keeps it in step. Nobody reads the new repository in production before cutover.
Daniel Weber, the integration administrator, starts the bulk load on 11.2 million documents with all their versions. To keep FileNet responsive for the agents, the batch runs with fewer workers during the day and more at night and on Sundays.
The bulk load took three weeks, and FileNet kept changing meanwhile. The first sync run carries over every change made since the load started: new documents, new versions, property updates. After that, each hourly run only covers the hour before.
For five weeks the sync runs every hour. The team watches the gap, then rehearses the switch end to end.
Grace follows the sync runs on a timeline. Once the backlog is gone, each run carries a few thousand changes and takes a few minutes. That duration is the number that matters for cutover weekend: it says how long the final run will take once writes are frozen.
A few changes need a person: a property value the mapping rejects, a name too long for the target, a content file missing in FileNet. Daniel works the exceptions list every morning, so none of them is still open on cutover weekend.
Two weeks before the date, the team plays the whole cutover on the pre-production copy, with the real runbook and a stopwatch. Melissa Grant, the service desk lead, brings five agents on Sunday morning to work real scenarios on the switched application.
The rehearsal finds one problem: the letter templates still pointed at FileNet. A step is added to the runbook.
Saturday evening, with the call center closed, the team runs the rehearsed runbook plus its one fix.
At 8:00 p.m. on Saturday the call center closes and Daniel freezes writes in the application. The final sync run carries over the last changes. The operations engine then produces the full reconciliation report: every document on its own line, with its FileNet identifier next to the new one.
At 9:05 p.m., Grace runs the go or no-go call against the runbook's criteria: reconciliation clean, no open exception, template fix in place. All green. Daniel points the customer service application and the letter templates at the new repository, through its API.
Had any criterion failed, the answer was simple: no-go, writes reopen in FileNet on Monday, and nothing has changed for the agents. After a go, FileNet stays read-only until its switch-off date.
The call center opens at 8:00 a.m. on Monday. Melissa watches the service desk queue with the migration team on standby. Agents open customer files, send letters and add signed forms as on any Monday. Old letters open in the viewer, in the browser, as before.
At 21:05 on cutover night, the final batch sits in one of three states, and each state gives Grace a different call to make.
Every document matches, the known source defects are listed, no exception is open.
Then: the lead calls go and the application is switched.A few changes from the last hours were stopped by a control, each one named.
Then: fixed within the window, or the lead decides to wait a week.Counts disagree, or a rule failed on many documents.
Then: no-go, so writes reopen in FileNet on Monday and the agents notice nothing.It does not book the weekend, freeze the writes or switch the application. It does not call go. Across the nine steps on this page, the cutover is decided by a named person, against criteria written in advance.
The engine loads, keeps the platforms in step and reconciles. The control is in the runbook and its rehearsal, so it holds on a Saturday night.
Measured on this FileNet exit and its eight weeks side by side. Your platform and your business hours will set your own.
Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.
Replacing a platform people use all day needs the CIO, the administrator on call and the service desk lead to agree. Each one is protecting something:
The business will not accept a weekend down, and the last upgrade proved them right.
On Saturday night, you are the one on the phone.
Monday morning is yours to answer for, whatever happened on Saturday.
With one week of changes. Run the bulk load of one class into a test space, then a week of sync runs, and measure how long each run takes. That number sizes your cutover.
FileNet stays the system of record the whole time, so the agents work as usual while you measure.
Next step
Tell us how your platform is used across the week. We will plan a test load and a week of sync runs with your team, and measure how long your cutover would need.