ZTABS modernizes legacy applications for Cape Town businesses in manufacturing, financial services, logistics and healthcare. Cape Town businesses operate critical systems built 10 to 25 years ago in VB6, Delphi, Access, Classic ASP and FoxPro on infrastructure approaching end of life. Developer availability for these legacy technologies is declining. ZTABS is remote-first by design from our Houston, Texas office.
Cape Town legacy modernization demand spans manufacturing ERP replacement, financial services policy administration, logistics fleet and warehouse management, healthcare practice management and professional services matter and document management.
Legacy app modernization in Cape Town at a glance
| Need | What we build | Key requirement |
|---|
| Manufacturing | Modern ERP replacing custom Delphi or VB6 | Production, inventory, SARS |
| Financial services | Policy and claims modernization | FSCA, SARB, POPIA |
| Logistics | Fleet and warehouse management | GPS tracking, customs |
| Healthcare | Practice management | HPCSA, POPIA, HL7 |
| Professional services | Matter and document management | Remote access, search |
South African legacy technology landscape
The typical Cape Town legacy application was built in the 2000s using technologies popular in South Africa at the time. Visual Basic 6 desktop applications still run in many businesses. Delphi was popular in South African enterprise development with many ERP and industry-specific applications. Microsoft Access database applications started as quick tools and became business-critical. Classic ASP web applications run on Windows Server 2003 or 2008 that reached end of support years ago. FoxPro and Clipper DOS-era database applications remain in use.
Finding developers who can maintain VB6, Delphi or Classic ASP is increasingly difficult. The risk of a single developer being the only person who understands the application is a critical business continuity concern. Actual assessed maintainability, dependencies, vendor support status and customer evidence of failure modes determine modernization urgency, not assumptions about business culture.
Manufacturing legacy modernization
Cape Town and Western Cape manufacturers operate custom Delphi or VB6 ERP systems built 10 to 20 years ago managing production, inventory and financials. These systems are deeply embedded in operations but run on unsupported technology.
Production management. Factory floor systems for production tracking, quality management and maintenance. Legacy Access databases or VB6 applications running on Windows XP machines on the factory floor. Modernization enables real-time production visibility, tablet-based data capture and IoT sensor integration.
Reporting. Management reporting from legacy databases using Crystal Reports, Excel macros and Access queries. Modernization replaces these with modern BI tools and real-time dashboards.
Retailer integration. Major South African retailers including Shoprite, Pick n Pay and Woolworths increasingly require EDI integration for orders and invoices. Legacy systems with limited or no EDI capability may require manual order entry. Modernization enables automated order processing with GS1 South African standards compliance.
Modernizing your Cape Town legacy ERP or business system?
Tell us about your legacy platform, data volume and integration requirements. We start with assessment covering business rule extraction, data analysis and modernization strategy.
Financial services legacy modernization
Cape Town financial companies operate legacy policy administration, claims processing and compliance systems.
Policy administration. Insurance policy management systems built in Delphi or VB6 managing thousands of policies. Complex business logic embedded in 100,000 plus lines of code. Modernization preserves business rules while enabling modern interfaces, API integration and mobile access.
Claims processing. Desktop applications with local databases lacking mobile access, customer self-service and modern integration. Modernization enables web-based claims with customer portal and API integration.
Compliance. Legacy systems not meeting FSCA and SARB regulatory requirements with limited audit trails, no data encryption and restricted access controls. Modernization builds compliance into the new system.
Logistics and transport legacy modernization
Cape Town logistics companies operate legacy fleet management, warehouse management and customs systems.
Fleet management. VB6 or Delphi desktop applications with local SQL Server databases. No mobile access means drivers call the office for delivery information. Modernization provides web and mobile applications with real-time GPS tracking.
Warehouse management. Access or VB6 warehouse applications without barcode or RFID support, no real-time inventory visibility and manual stock counts. Modernization enables modern WMS with mobile scanning and real-time inventory.
Customs. Legacy customs clearing applications with SARS eFiling integration through outdated methods. Modernization provides modern customs software with API-based SARS integration. Actual SARS customs API rights assessed per current specifications.
South African regulation
POPIA. Actual roles and lawful bases apply. Section 69 direct marketing permits consent or, where contact details were obtained in an actual sale of goods or services, marketing of own similar products with objection opportunity at collection and each subsequent message plus sender and opt-out contact identification. Section 72 cross-border transfers require recipient country qualifying law, BCR or binding agreement providing both similar processing protection and onward-transfer protections, or another statutory route. Section 71 applies where solely automated processing of personal information is intended to profile a data subject and produces legal or similarly substantial effects; exceptions include contract performance where the data subject's request is met or protective measures apply, or where the responsible party's own law or code provides suitable safeguards. Modernization addresses consent management, data retention and right-of-access mechanisms.
Eskom. Current reporting as of 23 October 2026 indicates 525 days without load shedding since 16 May 2025. This is not a permanent end or future uptime guarantee. Cloud deployment reduces exposure to local power disruptions but customer-side network, on-premises dependencies and agreed RTO and RPO targets still apply. Legacy on-premises servers were vulnerable to database corruption from unexpected power loss.
DMPR. The Department of Mineral and Petroleum Resources replaced the historical DMRE following cabinet restructuring. Mining regulatory requirements assessed per current published specifications where relevant.
SARS. VAT calculations, SARS reporting, eFiling integration where supported and customs integration assessed per current published specifications and customer credentials. Legacy systems with outdated tax calculation logic or reporting formats modernized for current requirements.
Strangler fig for South African systems
Seam selection. Manufacturing seams: production planning, inventory, sales and orders, financials, SARS reporting. Financial services seams: policy administration, claims, compliance. Logistics seams: fleet management, warehouse, customs. Each function extracted independently.
Single authoritative write. One system authoritative for each transaction type and period during coexistence. Financial dual-write dangerous for SARS reporting and regulatory compliance. CDC with versioning and conflict detection.
Reconciliation. Idempotency keys enforced by receiving side. Finite retries with DLQ. Unknown outcomes require reconciliation before replay, especially for SARS submissions, insurance premium settlements and payment processing.
Data migration methodology
Legacy database formats. SQL Server (most common), Access MDB files, Paradox (Delphi), FoxPro DBF files and custom binary formats. Character encoding issues from older systems using Windows-1252 rather than UTF-8. South African date formats. Legacy data types mapped to modern schemas.
Data cleaning. Years of accumulated data quality issues including duplicates, inconsistencies, missing values and invalid data. Cleaning before migration with agreed tolerance thresholds rather than migrating problems into the new system.
Data type mapping. Types, nulls, time zones, currency, rounding, identifiers, encoding, history and crosswalks reconciled. South African specific: ZAR currency precision, VAT calculation fields, SARS reporting identifiers, ID number handling per POPIA requirements.
Cutover rehearsal. Observable acceptance with measurable RTO, RPO and latency targets. Automated comparison with agreed record counts, checksums and tolerance thresholds. Parallel running for agreed workstreams and risk scope with rollback feasibility assessed after schema and data changes.
Inventory and discovery
Cape Town enterprise modernization begins with complete inventory: applications, users, scheduled jobs, database procedures, reports, file and EDI dependencies, vendor contracts, supported versus end-of-life versions.
Business rules discovered with users through representative transaction analysis. Often the legacy code is the only documentation. Original developers frequently unavailable. Reverse engineering business logic from code and user observation. Cape Town users deeply knowledgeable about the application quirks and workarounds provide invaluable input.
Illustrative Example
Hypothetical: Cape Town food manufacturer replacing custom Delphi ERP built in the mid-2000s
A Cape Town food manufacturer operates a custom Delphi application built in the mid-2000s managing production planning, inventory, sales orders, financials and SARS reporting. The original developer emigrated several years ago. Documentation outdated. The database runs on a physical server with limited backup and no tested recovery procedure.
Strangler fig modernization would extract sales and order processing first as a modern web service with retailer EDI integration for Shoprite and Pick n Pay. Production tracking modernized with tablet-based data capture replacing paper-based processes. Inventory modernized for real-time stock levels. Financial and SARS reporting migrated last with extensive parallel verification.
Assumptions: Delphi code accessible for analysis, production staff available for workflow validation, SARS reporting requirements documented, and parallel processing feasible. Residual risks include undiscovered business rules in decades of Delphi code, retailer EDI specification changes, SARS reporting format evolution and staff adoption. No guarantee of specific production efficiency, cost reduction or revenue improvement.
This is a hypothetical scenario for illustration. Actual scope, timeline and cost depend on your requirements.
Healthcare legacy modernization
Cape Town medical practices and groups operate legacy practice management, laboratory information and pharmacy dispensing systems.
Practice management. Patient records, appointment scheduling and billing on DOS-based or early Windows applications. Patient data on unsupported systems creates security and POPIA compliance concerns. Modernization provides cloud-based practice management with HPCSA compliance.
Laboratory systems. Custom Delphi or VB6 laboratory information systems for sample tracking, result management and reporting. Modernization provides modern LIMS with HL7 and FHIR integration.
Modernization approach selection
Cape Town enterprises need clear criteria for choosing between approaches. The choice depends on actual code quality, architecture, dependencies and integration requirements assessed per system.
Replatform. Moving to modern infrastructure while preserving core logic. Suitable when business logic is sound but technology is outdated.
Replace. Replacing custom application with commercial product. Suitable when function is now available as standard product such as SAP Business One or Sage.
Wrap. Modern API and UI layer around legacy application. Short-term solution while planning longer-term modernization.
Regression and testing
Representative business-critical paths: manufacturing production order with inventory and SARS VAT, financial services policy lifecycle with claims, logistics container tracking with customs clearance. Meaningful integration, performance and manual UAT with domain expert approval.
Cost and timeline
Legacy system modernization follows the published cost guide.
| Tier | Range | Timeline | Example |
|---|
| UI Modernization | $40K to $100K | 8 to 16 weeks | New frontend, API wrapper, improved UX |
| Re-Platforming | $100K to $250K | 16 to 32 weeks | Modern stack, containerization, cloud, data migration |
| Re-Architecture | $250K to $400K | 8 to 14 months | Decompose monolith, event-driven, modern data layer |
| Full Rebuild | $400K to $500K+ | 12 to 18+ months | Ground-up rebuild, agreed availability and cutover rehearsal |
Vendor comparison
Ranges reflect re-platforming a 10 to 15 year old business-critical system using a strangler fig approach, modern stack, API wrappers, phased data migration and regression harness.
| Vendor type | Typical cost | Timeline |
|---|
| Freelance or dev collective | $40K to $130K | 5 to 12 months |
| Offshore systems integrator | $60K to $200K | 8 to 14 months |
| Boutique modernization specialist (ZTABS tier) | $100K to $280K | 6 to 12 months |
| Big 4 consultancy | $300K to $1M+ | 10 to 18 months |
| SaaS replacement vendor | $50K to $200K implementation | 4 to 9 months |
Ranges are 2026 US-buyer guide-based planning benchmarks. Where applicable to the agreed migration, parallel-running infrastructure, senior-staff knowledge transfer and compliance revalidation for actual SOX, HIPAA or FDA requirements can add a planning allowance of $100K to $500K or more across vendor paths. Scope covers agreed engineering and revalidation support; any independent assurance engagement is scoped separately. These are engagement planning allowances, not an empirical market survey or an automatic surcharge for every system.
Proposal evaluation criteria
When evaluating vendor proposals for legacy modernization, assess these areas with named role responsibilities:
- Scope and system discovery. What applications, databases, integrations and scheduled jobs are inventoried? Who performs code archaeology, business-rule documentation and gap analysis? What is included versus excluded from the engagement scope?
- Integration and migration acceptance. What are the agreed data migration tolerances, reconciliation method and domain-owner sign-off criteria? Who builds and validates migration scripts? How are legacy formats, encoding and data quality exceptions handled and reported?
- Security and data rights. Who owns source code, data and deployed infrastructure after handover? What are data retention, deletion and portability terms? How is POPIA compliance responsibility allocated between customer and vendor?
- Verification, rollback and operations. What regression, performance and UAT methodology is proposed? What is the rollback plan after schema and data changes? Who monitors production post-cutover and for how long?
- Delivery ownership and cost dependencies. What is fixed-scope versus time-and-materials? What are infrastructure, licensing and parallel-running cost responsibilities? What triggers change orders? Are independent CPA SOC 2 opinions scoped separately from readiness preparation?
- Training, validation, support and working arrangements. Who trains end users, in what agreed working languages, and with what approved translated materials? Who provides ongoing support and at what SLA? What on-site arrangements are separately agreed if required? What customer staff participation is needed for domain validation and UAT?
Need help modernizing South African enterprise systems?
Share your legacy system landscape, POPIA requirements and modernization constraints. We provide a scoped estimate based on system complexity.
How delivery works
ZTABS is remote-first by design from our Houston, Texas office. Overlap with Cape Town business hours for coordination and review.
When ZTABS is not the right fit
- The system still works and nobody is asking for changes. Wait for a real forcing function before committing to modernization.
- SAP or Sage licensed implementation. A separately engaged ERP vendor partner handles licensed product implementation and configuration.
- On-site embedded team required for this engagement. ZTABS is remote-first by design. On-site staffing is a separately agreed arrangement.
- FSCA or SARB regulatory advisory for this engagement. Regulatory advisory is a separate engagement from platform engineering.
White-label AI products
ZTABS builds custom white-label AI products for clients to brand and resell. Cape Town technology companies can commission white-label AI platforms for distribution under their own brand.
Risks and mitigations
Legacy developer knowledge loss. Business rules documented and verified before developer departure. Knowledge transfer structured into discovery phase.
SARS compliance during transition. Agreed SARS reporting outputs and workstreams (VAT, EMP201, annual returns, customs where applicable) maintained through continuity and rehearsal arrangements during migration. VAT calculations verified through parallel operation within agreed reconciliation tolerances. Domain-owner sign-off on reporting continuity before each cutover phase. Fallback to legacy reporting path available until domain-owner acceptance of modernised outputs.
Data migration integrity. Automated verification with agreed record counts, checksums and tolerance thresholds confirmed by domain owners. Financial balances reconciled within agreed tolerances. Parallel running validates results before legacy decommission.
Logs and retention
Logs minimise and redact secrets and regulated payloads with actual retention and legal holds. SARS financial records retained per statutory requirements. POPIA personal data retention assessed per actual processing basis. Not all logs same retention period. ID numbers minimised where full identifier unnecessary.
Handover
Modernization handover includes runbooks, data lineage, licensing, support contacts and accountable owners. Manufacturing handover includes production system specifications and retailer EDI documentation. Financial services handover includes FSCA compliance documentation.
Ready to modernize your Cape Town legacy systems?
Share your legacy system landscape, POPIA requirements and modernization constraints. We start with assessment covering application archaeology, compliance mapping and modernization strategy.