Modular Replacement of 1C: How to Modernize Without Stopping Your Business

Full Migration Looks Great on Paper

Articles about a complete 1C-to-modern-stack migration in 6-10 months sound convincing. PostgreSQL schema, RLS policies, REST API, CI/CD — an engineer's dream. On paper.

For an average Moldovan distributor, full migration means:

• **€60,000-120,000 budget** upfront — not every owner can pull that from working capital • **6-10 months of development** — business keeps running, requirements shift • **Organizational risk** — accounting has used 1C for 10+ years • **All-or-nothing effect** — if the project stalls, money is spent and 1C is still needed

At AKDEV, we stopped selling full migration as a product. We sell **modular replacement**.

What Is Modular Replacement

1C stays as the accounting core. New modules are built from scratch and connected via an integration bus. Each module is a separate project with its own budget, timeline, and ROI.

Accounting stays in 1C. Operational processes move to the new stack.

Which Modules to Replace First

1. Warehouse (inventory, receiving, shipping)

The most common candidate. The warehouse works in real time — delays in 1C document posting are critical. Mobile terminals and barcode scanners — 1C's built-in language isn't designed for this.

**What we build:** a separate system on NestJS + Angular + PostgreSQL with a Flutter mobile app. Only totals (period turnover by SKU) sync with 1C. Valuation and cost remain in 1C.

**ROI:** warehouse stops waiting for document posting. Inventory — from 3 days quarterly to 1 hour on demand. Picking errors — from 2-3% down to 0.1%.

2. Sales and CRM

1C is inconvenient for sales managers: not designed for daily task management, calls, quotations.

**What we build:** CRM module on NestJS + Angular/CoreUI with pipeline, tasks, interaction history, quotes. Synced with 1C: counterparty catalog, contracts, mutual settlements.

**ROI:** order processing — from hours to minutes. Transparent sales pipeline. Fewer lost customers.

3. Procurement

Buyers see stock in 1C but not sales forecasts, reservations, or plans. Result: buying by gut feel.

**What we build:** procurement module with forecasting, automatic reorder point calculation, purchase request approvals.

**ROI:** 10-20% inventory reduction without losing Availability.

4. Document Workflow and Approvals

Any approval in 1C means a configuration modification. In a new module — a no-code workflow in 2 days.

Architecture in Practice

Integration Bus

No module touches the 1C database directly. Communication goes through RabbitMQ / REST API. Reference data sync — every 5-15 minutes. Stock levels — hourly. Documents — by event.

**Key rule:** the new module never waits for 1C synchronously. If 1C is down — orders are created, reservations are placed, sync happens when 1C returns.

Tech Stack per Module

• **Backend:** NestJS 10 (TypeScript) • **Frontend:** Angular 18 + PrimeNG / CoreUI • **Mobile:** Flutter • **Database:** PostgreSQL 16 • **Message broker:** RabbitMQ • **API:** REST + WebSocket for real-time

Budget and Timeline: Module vs Full Migration

• Full migration: €60,000-120,000 / 6-10 months / ROI in 2-3 years • Single module: €12,000-25,000 / 2-3 months / ROI in 4-8 months

**Case study:** warehouse module for a distributor with 50 users. Budget €18,000 (2.5 months). Result: shipping errors from 2.8% to 0.3%, inventory in 2 hours instead of 2 days. Payback — 6 months.

When Modular Replacement Doesn't Work

**Not suitable when:** • 1C is so customized that extracting a module is impossible • End-to-end analytics across departments is required in one system • Accounting and operations are inseparable • No capacity to maintain an integration bridge

In these cases, full migration may be cheaper than 5 years of integration bus maintenance.

Where to Start

A simple audit by three parameters: **Pain** (hours lost per month), **Isolability** (1-5), **ROI** (cost vs savings). Modules with high pain, good isolability, and fast ROI are first candidates. In 90% of cases — warehouse or sales.

If no module scores above 2 in isolability — full migration is the only option.

Summary

Modular replacement is a pragmatic approach: the business never stops, each module delivers its own ROI, entry budget drops from €60,000+ to €12,000-25,000, architecture evolves gradually.

Full migration is for when you have €120,000 and an owner ready to take a risk. Modular replacement is for everyone else.