Legacy System Integration
Legacy system integration for businesses whose older platforms lack modern APIs — wrapping database-level access, file-based integrations and older SOAP/EDI interfaces so that modern systems can exchange data with them. Bridges the gap between legacy infrastructure and new digital tools without replacing the legacy system.
Legacy system API wrapping
API wrapper layer built around a legacy system that has no modern API — exposing the system's data and functionality through a clean REST or GraphQL interface that modern applications can consume, without modifying the legacy system itself.
- API facade design: clean modern interface over legacy internals
- Database-level read wrapper for legacy systems with no API
- SOAP to REST translation proxy
- Screen-scraping automation for systems with no API at all
- Authentication bridge: legacy auth translated to JWT or API key
- Response caching: reduce load on legacy system from API traffic
- Throttling to protect legacy system from API traffic spikes
- API wrapper documentation matching modern API standards
Data migration & transformation
Data migration from legacy systems to modern platforms — extracting data from old databases and file stores, cleaning and transforming it for the new system's data model, validating quality and loading it with full auditability of what was migrated and what was changed.
- Source data profiling: understand quality, volume and structure
- Data model mapping: legacy fields to new system fields
- Transformation rules for data quality issues in legacy data
- Pilot migration with quality validation before full run
- Full migration with rollback capability
- Migration audit: every record migrated with its transformation
- Post-migration validation: record counts and sample spot-checks
- Cut-over planning to minimise downtime during switch-over
Old-to-new system bridging
Integration bridge for parallel operation periods where the legacy system and new system must run simultaneously — keeping data in sync between the two during transition, allowing gradual migration of users and processes without a hard cutover that risks business disruption.
- Dual-write integration: new records written to both systems
- Backfill sync: historical legacy data accessible in new system
- Read routing: new system falls back to legacy for missing records
- User migration planning: migrate teams gradually, not all at once
- Feature flag control: which users are on new vs. legacy system
- Data consistency verification across both systems
- Traffic mirroring: monitor for discrepancies between systems
- Legacy system decommission plan with data retention compliance
Database-level integration
Direct database integration for legacy systems where no API exists and screen-scraping is not viable — reading from and writing to the legacy database with appropriate safeguards, using read replicas to avoid impacting production performance.
- Read replica database connection to avoid production load
- Stored procedure or view-based access to avoid direct table writes
- Schema documentation and change impact analysis
- Query optimisation for integration workloads
- Connection pooling and timeout handling
- Database-level audit logging for compliance
- Transaction management for multi-table writes
- Database vendor support: MySQL, MSSQL, Oracle, PostgreSQL, Sybase
FTP/SFTP automation
Automated FTP and SFTP file exchange with legacy systems, banks, logistics providers and government systems that still communicate by scheduled file transfer — picking up files as they arrive, processing them and depositing output files reliably.
- Scheduled FTP/SFTP file pickup and processing
- New file detection: trigger processing on file arrival
- File format parsing: CSV, fixed-width, XML, JSON
- File archiving after successful processing
- Failed file isolation and error alerting
- Output file generation and SFTP deposit
- Encrypted file handling: PGP decryption on pickup
- SFTP key management and rotation
Flat-file & EDI processing
Flat-file and EDI document processing for businesses exchanging structured messages with trading partners, banks and logistics providers — parsing EDI (EDIFACT, X12), CSV and fixed-width formats and translating them to and from the internal data format.
- EDIFACT and ANSI X12 EDI parsing and generation
- CSV and fixed-width flat file processing
- EDI document types: orders (850/ORDERS), invoices (810/INVOIC), ASN (856)
- Trading partner mapping: their format to internal format
- Validation against EDI standard and trading partner specification
- Acknowledgement generation (997/CONTRL)
- EDI document archive per trading partner
- Error reporting to EDI team with document and error detail