In the ever more complex ECM/WCM application landscape, it is difficult to oversee the implications of a platform migration. Synchronization solutions offer an intermediate solution for a more smooth transition in complex environments.
In a very interesting article on Computable (in Dutch), the idea is proposed to use content integration as a stepping-stone to content migration.
The underlying idea is twofold:
While I fully agree with the scenario described, I think that for most organizations a full integration solution is overkill for the problem at hand. A typical scenario we see at migrations is the implementation of a one-way synchronization between legacy systems and the new ECM/WCM platform.
Data entered into one of the legacy systems is then automatically pushed to the new system. This solution has a number of benefits over the one described above:
This scenario works typically very well where the new platform is initially primarily used for exposing content.
Whether organizations choose integration or synchronization, both have clear benefits as a first stage transition, or as part of a migration. There is no content freeze, there is extra time to (re) build functionality, and the organization can start making use of the new system at a much earlier stage.
Synchronization might be just what you need: