Migrate from NetCat to Bitrix: Preserve Traffic and Data

You are running a site on NetCat that has been in operation since 2012? Chances are you’ve already run into issues: slow page loads (2–4 seconds), outdated visuals, and difficulties integrating a modern tech stack. We have completed over 50 successful migrations from NetCat to 1C-Bitrix — and each time we encountered a non‑standard data storage architecture. After migration, page load speeds on Bitrix are 3–5 times higher thanks to tagged caching, and SEO traffic remains at the previous level if 301 redirects are properly configured. Our experience — over 5 years on the market, 50+ completed projects — guarantees data integrity and full documentation after launch.

How to Migrate Data Without Loss?

NetCat’s data structure is fundamentally different from Bitrix’s. NetCat uses the concept of “components” — similar to Bitrix information blocks. Each component has its own database table with a name like netcat_main_<component_id>. That means there is no single “elements” table — each content type lives in its own table, whose schema is defined by the component settings.

Key NetCat system tables:

• netcat_main_catalogue — site section catalog
• netcat_main_component — component types (analogous to infoblock types)
• netcat_main_field — component fields
• netcat_main_sub_class — subclasses (binding components to sections)
• nc_file — file archive

For each component with ID=5 there is a table netcat_main_5 containing its data. Before migration, you need to extract the schema of all such tables and build a mapping to Bitrix information blocks.

Extracting the Structure via SQL

-- Get all components and their fields SELECT c.Component_ID, c.Component_Name, f.Field_Name, f.Type FROM netcat_main_component c JOIN netcat_main_field f ON f.Component_ID = c.Component_ID ORDER BY c.Component_ID, f.Priority; -- Get data for a specific component SELECT * FROM netcat_main_5 WHERE Catalogue_ID IN ( SELECT Catalogue_ID FROM netcat_main_catalogue WHERE Sub_Class_ID = 12 ) AND Hidden = 0; 

NetCat field types (string, text, integer, float, checkbox, file, image, date, select) map to Bitrix infoblock property types: S, S/html, N, N, L, F, F, D, L respectively.

Site Structure and Navigation

Section hierarchy in NetCat is stored in netcat_main_catalogue with the field Parent_Sub_Class. This tree must be recreated in Bitrix — either as infoblock sections (CIBlockSection) or as a site structure via menus. Depending on the content type of each section, you choose the appropriate approach.

Moving Files and Images

NetCat stores files in the /netcat/files/ folder with its own subfolder structure. The nc_file table stores metadata: file name, path, type. During migration, files are transferred using CFile::SaveFile() in Bitrix, creating entries in the b_file table.

Images in NetCat are often stored directly in an HTML content field with absolute paths. After transfer, all such paths need to be updated — via SQL replacement in the database or a script that iterates through infoblock elements.

Forms and Feedback

NetCat has a built‑in form module (netcat_form_* tables). Forms are moved to the Bitrix “Web Forms” module or implemented using the bitrix:form.result.new component. Accumulated submissions are migrated only if critical for business; otherwise they are archived.

What About SEO Positions After Migration?

URLs in NetCat are generated by their own rules and often do not match the URLs that will be in Bitrix. Before the move:

1. Export all old site URLs (via a crawler or from the netcat_main_catalogue table)
2. Build a mapping of old URL → new URL
3. Set up 301 redirects via .htaccess or the bitrix:redirect module
4. Transfer title and description from the Sub_Class_Otsek field and associated SEO fields

Typical Timeframes

The NetCat template and design are not transferred — they are rebuilt from scratch on a Bitrix template. This is standard practice: the outdated site’s visual part usually requires an update along with the platform change.

NetCat vs 1C-Bitrix in Numbers

What Is Included in the Work

• Audit of the old site: inventory of components, fields, files
• Creation of a migration plan with data mapping
• Transfer of all data: items, sections, files, users
• Configuration of 301 redirects and URL mapping
• Testing of migrated functionality and integrations
• Delivery of full documentation for the new project
• One hour of post‑launch support for resolving unexpected situations

Contact us for a free estimation of your project. We guarantee data integrity, set up 301 redirects, and help with initial indexing. Get a consultation — write to us.