Worklog for task "Migration of bizneshelper.ru from Ruby to haih-cms"

Stage: The website has been essentially completely rebuilt on the new system

The main technical overhaul of bizneshelper.ru is complete. The new website is built on haih-cms and no longer depends on having to replicate the old Ruby architecture as a working system.

At the same time, some of the internal page styling was intentionally not fully restored. Trying to achieve an exact match with the old design would offer little practical value at this point: it would require extra time, lock in old visual solutions, and ultimately only complicate the development of a new design.

The current stage of the project is not about final visual polishing, but about testing whether the website can re-enter search visibility and recover organic traffic, which is currently virtually non-existent. If visibility and traffic begin to recover, it will make sense to develop the visual part as a separate next stage on the new architecture.

The main immediate priority shifts to working with content: migration, normalization, updating, internal linking, SEO, and AI-driven processing of materials.

Important conclusion regarding migration costs

In practice, the main overhaul took about 3–4 days, but a significant portion of this time was spent not on creating new functionality, but on bypassing the quirks of the old technical implementation. The legacy site turned out to be significantly more difficult to migrate than it should have been for a comparable volume of content.

The main sources of unnecessary complexity:

• too many specialized entities and tables;
• different storage models for essentially similar types of content;
• separate presentation logic for different entities;
• custom CSS for many page types and components;
• accumulated WYSIWYG/HTML quirks that had to be normalized during import;
• high coupling between the data structure and specific old templates.

This is practical confirmation of the adopted architectural decision: unifying content entities around Concept is not for the sake of abstract schema neatness, but so that future changes do not require going through such a volume of special-case logic again.

From the project's perspective, this is precisely why the result is important: despite the poor internal state of the legacy system, the new version was assembled in just a few days, and future development can now proceed on top of a significantly simpler and AI-friendly environment.