Own case
SISCON ERP migration: 15 weeks, 0 days of downtime
We left GeneXus with our own management system, module by module and without stopping operations.
Context
SISCON ran its internal management system on GeneXus. It is the system the company itself is managed with.
Challenge
Leave GeneXus without stopping operations and keep the data with its identifiers.
Solution
We migrated module by module with route-based cutover: a single entry point splits traffic between the legacy and the new system. Every change was integrated with review and verified with automated tests.
Verifiable result
- 782 changes integrated with review.
- Data migrated with identifiers preserved.
The ERP today
What SISCON's ERP looks like today
These are the modules of the management system SISCON runs on, as they appear in its side menu.
- Invoicing (Facturación): vouchers, payment complements, cancellations and CFDI lookup.
- Payroll (Nómina): payroll runs, receipts, incidents, vacations and tax tables.
- CRM: leads, opportunities, quotes, pipelines and dashboard.
- Finance, Expenses and Treasury: profitability, expense capture and categorization, bank accounts and deposits.
- HR (RH): candidates, employees, contracts and project assignments.
- Receivables and payables (CxC, CxP): accounts receivable, accounts payable and suppliers.
- Security (Seguridad): roles, permissions, audit and AI agent.
- Also: Sales, Assets, Catalogs, SAT catalogs, Diagnostics and Platform.
Next step
Want to see how it would look with your system? We start with a measured sample: 5 to 10 screens turned into a verifiable specification.