Some migrations are just migrations. This one was not.
Acuorleggero was the site that started the whole thing. Before Lubinik had a name, before there was a parent theme, before there was a core plugin, before addons became a real architectural idea, there was a small BnB website that needed to exist properly.
At the time, I did not think I was starting a framework. I was just trying to build a site without fighting WordPress more than necessary. I needed rooms, practical information, galleries, local attractions, places to eat, booking links, contact details, and a design that felt like the actual place.
So I made a theme. Then I made a plugin. Then I kept noticing that some parts were site-specific and some parts clearly were not. That little distinction eventually became one of the foundations of Lubinik.
The site before the system
The original Acuorleggero site was built before Lubinik really existed. It already contained the seeds of the later architecture, but they were still tangled together.
The BnB logic was there. The content model was there. The idea of reusable sections was there. The need for custom data was there. But it was still a first version: useful, working, and a little too close to the original problem to be clean.
That is usually how real systems begin. Not from a perfect diagram, but from something concrete that makes you ask better questions.
Which parts belong to this site, and which parts am I going to need again?
That question followed me into the first refactors, then into the parent theme, then into the core plugin, then into the BnB addon. Acuorleggero did not just use the first version of that thinking. It caused it.
Coming back with better tools
Migrating Acuorleggero into Lubinik was funny because the new system did not feel unrelated to the old site. It felt like the old site had grown up somewhere else and was finally ready to come back.
The new version now runs on the Lubinik parent theme, the core plugin, the BnB addon, and a cleaner child theme. The data lives in proper WordPress structures. The reusable pieces are no longer trapped inside one site. The design can be handled as a child-theme layer instead of being mixed into the business logic.
The migration was not magic. There were still the usual practical details: importing content, photos, contact settings, menus, the hero, local attractions, restaurants, amenities, structured data, visibility rules, and all the little visual differences that only appear when you compare the old site and the new one side by side.
But this time, the work had somewhere to go.
The strange satisfaction of a loop closing
There is something satisfying about migrating the origin site into the system it accidentally helped create.
Acuorleggero pushed me to build a first theme and plugin. That first theme and plugin pushed me to separate reusable code from project-specific code. That separation became Lubinik. And now Lubinik can host Acuorleggero properly, with the BnB addon carrying the domain logic that began there in the first place.
It is not a dramatic public milestone. It is a small technical one, but it matters to me because it proves something quiet: Lubinik is not only useful for new projects. It can also absorb its own past.
That means the framework is not just a cleaner rewrite. It is a way to preserve the useful parts of older work without dragging all the old mess forward forever.
What this taught me
This migration reminded me that architecture is not only about starting new things neatly. It is also about giving old things a better place to live.
The first version of a project often contains more truth than polish. It knows the real constraints. It knows the content. It knows the client-side awkwardness, the images that actually exist, the sections that are needed, and the tiny bits of logic that no abstract framework would have invented alone.
Lubinik exists because I kept listening to those concrete problems instead of pretending they were noise.
So yes, Acuorleggero is now officially migrated to Lubinik. And that feels less like moving a site from one stack to another, and more like putting the first chapter back into the book after finally writing the rest of the outline.
