SnoutScoop was a different kind of migration for Lubinik.
Acuorleggero came back into Lubinik as an origin story. It was the BnB site that helped create the first version of the system. SnoutScoop was not that. It was not asking for a custom accommodation model, a shelter addon, or a new domain layer.
It was a blog.
That made the migration useful in another way. It tested whether Lubinik could avoid overreacting.
The old site had accumulated history
The old SnoutScoop site lived in a very normal WordPress situation: Hello Elementor, Elementor, Elementor Pro, translation plugins, SEO plugins, cache tools, media utilities, WooCommerce, social feed plugins, and a lot of plugin-shaped history around the actual content.
Some of that had made sense at the time. A site grows, experiments happen, tools get added, and eventually the stack starts to describe all the routes the project has taken instead of the thing the project needs now.
The important part was still there, though: the posts. SnoutScoop had a real archive of dog-focused articles, categories, tags, images, and editorial ideas. The migration was not about throwing that away. It was about removing the old weight around it.
Not an Elementor migration
The first useful decision was to not make this an Elementor migration.
The blog posts were mostly standard WordPress posts with usable Gutenberg-style content. That meant the clean path was not to recreate the old frontend builder setup. The clean path was to export the content, preserve the useful metadata, remap the media, and let the new site be a Lubinik site.
The source export captured posts, pages, users, attachments, terms, menus, SEO metadata, Elementor metadata, and URL mappings. The Elementor data was kept as reference, not as a runtime dependency.
- 46 posts came over;
- categories and tags were preserved;
- featured images and inline media had to be remapped;
- menus were exported and prepared;
- pages were kept for later review instead of being blindly rebuilt.
That felt like the right amount of migration. Not too little, because the archive mattered. Not too much, because the old plugin ecosystem did not need to become the new foundation.
The media was the real migration
As usual, the hard part was not the database rows that looked tidy in the plan.
It was the media.
The old uploads folder had normal attachment files, generated thumbnails, plugin folders, Elementor traces, WooCommerce leftovers, cleanup folders, and files that only made sense if you knew the history of the site. Copying everything would have brought the mess forward. Importing only what WordPress knew about was cleaner, but then URLs, featured images, and inline references had to be mapped properly.
One post made that very obvious: the Midjourney canine fashion article. It had hundreds of image references and gallery-like groups. That kind of article is where a lazy migration shows its cracks immediately.
So SnoutScoop got its own export, import, verification, media rename plan, and media usage audit. This was not glamorous work, but it is the kind of work that decides whether a migration feels solid later.
The child theme carried the identity
The target site now has a SnoutScoop child theme: lubinik-child-snoutscoop.
That is where the site-specific layer belongs. Blog layouts, archive views, single post presentation, design packs, gallery behavior, SEO defaults, structured data, and editorial configuration can live there without making the Lubinik parent theme pretend it knows every future site.
This is one of the quiet rules Lubinik keeps teaching me: a project does not always need a new addon. Sometimes native WordPress posts, a clean child theme, and the shared Lubinik foundation are enough.
What this migration taught me
SnoutScoop proved something small but important about the framework.
Lubinik should not make every site more complicated just because it can. If the correct model is the boring WordPress model, the framework should support that calmly. Posts, categories, tags, media, menus, pages, SEO, structured data, and a child theme are not lesser architecture. They are the right architecture when the site is a blog.
The migration also exposed a different problem, though: SnoutScoop had not only become heavy to maintain technically. It had become heavy to publish.
That became the next post.
