bizneshelper.ru — modernization and migration to haih-cms

Context

bizneshelper.ru is an active website with a long history, a large volume of expert content, and a legacy implementation based on Ruby on Rails 3.2.

An analysis of the original site revealed a typical problem of old CMSs: a product that works on the outside can hide under the hood many specialized tables, repeating fields, and exceptions. This directly increases maintenance costs and makes even simple changes less attractive for developers and project owners.

Modernization Goal

Migrate the site to haih-cms as the new and sole working system, preserving useful data and content without reproducing the legacy architecture.

The old Ruby site remains as a backup and data source for verification. Constant parallel operation of the two systems and full backward compatibility with the entire historical implementation are not required.

Main Architectural Principle: Practically Everything Becomes a Concept

The substantive entities of the old site — pages, services, cases, FAQ questions, news, employees, and other materials — are reduced as much as possible to the universal Concept model.

The differences between them should not automatically mean a separate table, a separate CRUD, and a separate set of infrastructure fields. The new side uses a minimal common content contract: name, description, intro, content, while URIs, visibility, type, relationships, and other system-wide capabilities work uniformly.

The legacy DB is viewed as a source of initial facts, but not as a model for the target schema.

Import: Data is Preserved, Structure is Collapsed

During import, specialized legacy fields are gathered into a single primary Concept content.

For example, case data from customer, problem, solution, result, review, and comment becomes the initial content of a single entity rather than six fields of the new CMS.

Historical URLs are supported separately via RedirectRule if necessary, so URL compatibility does not clutter the content model.

A decision was made to transfer all useful old site content into Concepts.

Main Effect: AI-driven Content

Initial import is just the beginning. After the migration, the AI agent can receive:

• initial data of the legacy record;
• the created new Concept;
• general project context.

And then update the page as a single document: structure, format, update, improve presentation and internal linking while preserving verified facts.

The key advantage of unification is that a single AI pipeline is applicable to different types of content. The agent does not need to know dozens of legacy tables and special field sets.

Thus, haih-cms becomes not just a new CMS, but an AI-native content layer.

Connection to a Broader Technological Shift

This project well illustrates the thesis from the material «Specialist productivity growth requires the development of the business technological environment»: the productivity growth of specialists and AI does not yield full effect if the technological environment continues to force them to spend time bypassing legacy limitations.

A separate public analysis of this approach: Unified Data as the Foundation of AI-driven Projects — VietnamGuru and BiznesHelper.

Current Areas of Work

Main Task

• Migrate bizneshelper.ru from Ruby to haih-cms — general coordination of the transition to the new system.

Data and Architecture

• Unify bizneshelper.ru content into the Concept model — target data model.
• Import legacy content into Concepts and prepare AI enrichment — transferring data from the old DB.
• Transfer all useful legacy content to Concepts and media — complete transfer of preserved content and files.
• Develop an AI process for updating imported Concepts — a single AI pipeline for further editorial processing.
• Make universal rendering and routing of Concepts — the general public layer of the new CMS.

User Features

• Reimplement forms and current public integrations from scratch.
• Simplify the feedback form and replace the questionnaire with an AI agent.
• Implement search by Concepts.
• Rebuild the "FAQ" section on Concepts.

SEO and Launch

• Prepare an SEO map of significant URLs and redirects.
• Form the SEO layer of the new site and ensure search engine migration.
• Conduct functional and content testing.
• Prepare the switch to haih-cms and backup rollback.
• Conduct post-migration verification.
• Boost Lighthouse metrics.

Substantive and Commercial Modernization

• Repackage the public structure of services and cases.
• Update the main page and key entry points.
• Update public information and trust elements.

Principle of Publicity

Only general technical, architectural, and product information is recorded in the concept and related public entities. Internal commercial data, credentials, personal information, and other sensitive data are not published.

Related Entities

• Project: bizneshelper.ru.
• Case: Unified Data as the Foundation of AI-driven Projects — VietnamGuru and BiznesHelper.
• Related Example: VietnamGuru.