SUSE successfully connected Brandfolder to Lolly and used that connection to introduce Lolly alongside an existing content library and approval practices. The integration supported change management for administrators responsible for different content approvals before a planned move away from Brandfolder.
This account records the Lolly maintainer's deployment experience, reported on 31 October 2026. The migration target is the end of December 2026. The connection is in use; migration is planned, not reported complete.
Start from the system people already administer
Introducing a creative platform also introduces decisions about who curates assets, which content needs approval and where people go to make the next version. An existing DAM contains both files and established administrative responsibilities.
At SUSE, the Brandfolder integration helped Lolly inherit that existing system during adoption. Administrators could work through the changes to their content-approval responsibilities while the connection supplied continuity. The value was the time and continuity available for change management, alongside access to the library.
What the connector provides
The public Brandfolder source guide describes the implementation: assets enter the Work catalog as references, selected by exposure rules, and Brandfolder remains the source of record while connected. Current attachments keep their file identities when selected in Lolly.
That technical contract explains the supported integration. It does not establish which optional field or action the SUSE deployment exercised. The maintainer's account confirms successful use and its role in adoption; the two Brandfolder availability-field mappings still have a separate live-check requirement in the guide. Outbound Brandfolder delivery is a different adapter with its own qualification requirements.
What is established, and what remains to demonstrate?
| Item | Status as of 31 October 2026 |
|---|---|
| Brandfolder connected to Lolly at SUSE | Successful use reported by the Lolly maintainer |
| Continuity during adoption | The integration helped inherit the existing system |
| Administrator change management | Supported administrators responsible for various content approvals |
| Migration away from Brandfolder | Planned for completion by the end of December 2026 |
| Quantified time, cost or adoption improvements | No measurements published in this account |
| Completed migration and preservation of every source record | Not established by this account |
How another organisation can apply the approach
Identify the administrators and approval responsibilities before connecting the library. Introduce one bounded production workflow, retain the existing source authority and test access and withdrawal. Use the adoption period to decide which responsibilities should stay with the DAM and which belong with production or delivery.
Keeping the DAM is a supported outcome. Moving later is another choice, with its own checks for originals, metadata, permissions, history and recovery. The SUSE experience supports connecting first and allowing time for organisational change; it is not a promise that another tenant will have the same mappings or migration requirements.
Continue with Use Lolly with your existing DAM, Plan a DAM transition or the Brandfolder setup guide.