ZTABS modernizes legacy applications for Lisbon businesses — migrating PHP, .NET, Java, and Access database systems to modern, cloud-native applications. Preserve your business logic while upgrading technology.
Lisbon businesses carry a specific legacy technology burden shaped by Portugal's technology adoption patterns over the past 20 years. The legacy landscape in Lisbon includes: PHP applications (the dominant web technology in Portugal from 2005-2015 — many Lisbon businesses running critical operations on PHP applications built by agencies or freelancers who are no longer available. These applications: running PHP 5.x or early PHP 7 on shared hosting, with no automated tests, no version control, and no documentation), .NET Framework applications (built during Portugal's enterprise technology adoption wave of 2008-2015 — Windows Server, SQL Server, IIS. Many running on Windows Server 2012 or 2016, approaching or past end of Microsoft support. These applications: typically departmental tools built by Portuguese IT consultancies, now maintained by internal IT teams who inherited the code), Java applications (enterprise systems built for Portuguese banks, insurance companies, and government — often running on Tomcat or JBoss. These applications: complex, deeply integrated with business processes, and terrifying to touch because nobody fully understands the codebase), Microsoft Access databases (possibly the most common legacy system in Portuguese SMEs — Access databases built by an employee who "knew computers," now running mission-critical business processes. The database: growing beyond Access's limits, crashing periodically, and the original creator long departed), and custom ERP modules (modifications to Primavera or PHC — Portugal's dominant ERP systems — built 10-15 years ago. The modifications: implemented in older programming paradigms, poorly documented, and increasingly incompatible with ERP vendor updates). The modernization urgency is growing. Security vulnerabilities (PHP 5.x and .NET Framework applications receiving no security patches — running on unsupported operating systems with known vulnerabilities), integration limitations (legacy applications unable to connect with modern SaaS tools, APIs, and cloud services — requiring manual data transfer that wastes time and introduces errors), talent scarcity (finding developers who can maintain legacy PHP, .NET Framework, or Access applications in Lisbon is increasingly difficult — the talent pool has moved to modern technologies), performance constraints (applications built for 50 users struggling with 500 — response times degrading, databases growing beyond their design capacity, and workarounds accumulating faster than improvements), and compliance pressure (GDPR requirements for data portability, deletion, and audit trails — difficult to implement in legacy applications that weren't designed with these requirements in mind). But modernization carries risk. The legacy application works — badly, slowly, with workarounds — but it works. Every business process that depends on it has adapted to its quirks. Modernization must preserve the business logic that users depend on while upgrading the technology. Reckless modernization (rebuild everything from scratch, hope it works) has destroyed more businesses than it has saved. Careful modernization (understand the existing system deeply, preserve what works, upgrade what doesn't) is the only responsible approach.
Lisbon's legacy modernization demand comes from SMEs on Access/PHP, mid-market companies on .NET/Java, and enterprises updating custom ERP modules. SMEs (10-100 employees): the Access database and PHP application problem. Thousands of Lisbon SMEs running critical processes on systems that were built as quick solutions and became permanent. SME legacy profiles: the Access database that runs the business (a recruitment agency with a 15-year-old Access database tracking 40,000 candidates — the database: 1.2GB, crashing weekly, and the frontend forms: so complex that only 2 people in the company understand how to use them. The business: completely dependent on this database for operations), the PHP CRM (a Lisbon services company using a PHP application built in 2011 for customer management — the application: running on PHP 5.6, hosted on a shared server with no SSL, containing 12 years of client data. The original developer: unreachable. No documentation. No tests. The company: unable to add features or fix bugs without risking the entire system), and the Excel macro monster (an accounting firm with an Excel workbook containing 200+ VBA macros — performing data transformations, report generation, and data validation. The workbook: requiring Excel 2013 specifically — newer versions breaking certain macros. The firm: unable to upgrade Office because of macro dependency). Mid-market companies (100-500 employees): the .NET Framework and Java application problem. Companies that invested in custom software 10-15 years ago and now need to modernize. Mid-market legacy profiles: the .NET departmental application (a Portuguese logistics company with a .NET Framework 4.5 application for shipment tracking — the application: running on Windows Server 2012 R2, SQL Server 2014, and IIS 8.5. The server: approaching end of extended support. The application: handling 200 daily users and 50,000 shipments per year. Migration to .NET 8 or complete rewrite: the strategic decision facing the company), and the Java enterprise system (a Lisbon insurance company with a Java application for policy management — built on Java 6, running on Tomcat 6. The application: processing 15,000 policies and generating regulatory reports for ASF — Autoridade de Supervisão de Seguros e Fundos de Pensões. Any modernization must maintain regulatory reporting accuracy and data integrity). Enterprises (500+ employees): custom ERP and legacy system portfolio modernization. Portuguese enterprises carrying portfolios of legacy systems accumulated over decades. Enterprise legacy challenges: Primavera/PHC customizations (custom modules built 10+ years ago — tax calculation modifications, industry-specific workflows, and integration connectors that break with every ERP update. Modernization: either rebuilding the customizations for the current ERP version or extracting the custom functionality into a separate, modern application that integrates with the ERP via API), and multi-system integration (enterprises running 15-20 different systems — some modern SaaS, some legacy on-premise — with manual processes bridging the gaps. Modernization: building an integration layer that connects all systems, or replacing multiple legacy systems with a unified modern platform).
Our Lisbon legacy modernization follows a low-risk methodology: assess, plan, execute incrementally, and validate continuously. Assessment (weeks 1-2): understanding the legacy system. We analyse the existing system comprehensively: codebase analysis (for applications with available source code — code quality assessment, dependency analysis, architecture mapping, and technical debt inventory. For applications without source code or documentation — reverse engineering functionality through user observation and database analysis), database analysis (schema examination, data volume assessment, data quality audit, and relationship mapping. For Access databases: identifying design limitations — table size limits, query complexity limits, and multi-user access issues), business logic extraction (the most critical phase — understanding what the application actually does, not what documentation says it does. Business logic often lives in: database stored procedures, application code, spreadsheet formulas, email rules, and the heads of experienced users. We document all business logic regardless of where it currently resides), integration mapping (what other systems connect to the legacy application — data flows in and out, frequency of data exchange, and the format and protocol of each integration), and user workflow documentation (how users actually use the system — the screens they visit, the data they enter, the reports they generate, and the workarounds they use for system limitations. User workflows inform the modern application's UX design). Modernization strategy (week 2-3): choosing the right approach. Not every legacy system should be rewritten from scratch. We evaluate three strategies: re-platform (move the application to modern infrastructure without changing functionality — e.g., migrating a .NET Framework application to .NET 8, or migrating an Access database to SQL Server with a web frontend. Lowest risk, fastest timeline, but limited improvement in functionality), incremental replacement (the strangler fig pattern — building modern replacements for individual features while the legacy system continues operating. New features served by the modern application; old features gradually migrated. Risk spread over time, with the legacy system as a safety net throughout), and complete rebuild (building the application from scratch on modern technology — using the business logic extracted from the legacy system as the specification. Highest risk and longest timeline, but the best outcome for systems where the architecture is fundamentally incompatible with modern requirements). Our recommendation: based on the specific system. We default to incremental replacement for large systems (lower risk) and complete rebuild for smaller systems (the strangler fig overhead isn't justified for applications with fewer than 20 features). Development (weeks 3-14): building the modern application. Technology stack: Next.js (web application — replacing Windows Forms, Access forms, or PHP pages with modern, responsive web interfaces), PostgreSQL (replacing SQL Server, Access, or MySQL — with data migration scripts that preserve all historical data), and Node.js or Python (API layer — implementing the business logic extracted during assessment). Data migration: the most risk-sensitive phase. We migrate data iteratively: schema migration (designing the modern database schema — normalising data that was denormalised in the legacy system, adding constraints that the legacy system didn't enforce, and preserving data relationships), data transformation (converting legacy data formats to modern formats — date formats, character encodings, numerical precision. For Portuguese data: handling Portuguese character encoding — many legacy systems using ISO 8859-1 or Windows-1252, requiring conversion to UTF-8), data validation (comparing migrated data against source data — automated record counts, checksum verification, and sample-based manual verification. Every row: accounted for), and parallel running (the modern system and legacy system running simultaneously for 2-4 weeks — same data entering both systems, results compared daily. Discrepancies investigated and resolved before cutover). Cutover and decommission (weeks 12-16): switching to the modern system. Cutover: planned for a low-activity period (Friday evening or weekend), with a defined rollback plan (if the modern system fails during the first week, revert to the legacy system — the rollback capability maintained for 2-4 weeks post-cutover). Legacy system: not immediately decommissioned. Read-only access maintained for 6-12 months (users may need to reference historical data in the legacy format, and compliance may require access to the legacy system's audit trails). Final decommission: after confirming that all data has been migrated and all compliance requirements are met.
Recruitment / Human Resources
A Lisbon recruitment agency (45 employees, specialising in IT and engineering recruitment for Portuguese and European companies, EUR 3.8M annual revenue) was running its entire operation on a Microsoft Access database built in 2009. The database: (1) Scale problems: 42,000 candidate records, 8,500 company records, 23,000 placement records, and 15 years of communication history. Total database size: 1.4GB (Access's recommended maximum is 2GB — approaching the hard limit with every monthly data load). Performance: queries that took 2 seconds in 2015 now took 15-30 seconds. Opening the candidate search form: 8 seconds. Running the monthly billing report: 4 minutes. Compact and repair (Access's maintenance operation): required weekly, taking 20 minutes during which the database was unavailable. (2) Multi-user failures: 18 consultants accessing the database simultaneously via a shared network drive. Access's multi-user capability: designed for 5-10 concurrent users, failing at 18. Record locking conflicts: 5-10 per day (consultant A trying to update a record that consultant B has open — Access showing a generic error message that confused users and sometimes resulted in lost data). Database corruption: approximately once per month — caused by a network interruption during a write operation. Recovery: restoring from the previous night's backup and losing a day's work. (3) No remote access: the database accessible only from the office network. Post-COVID: 60% of consultants working hybrid. Remote workers: unable to access the database from home. Workaround: consultants copying relevant data to spreadsheets before leaving the office, working from the spreadsheet at home, and re-entering changes into Access the next day. The workaround: creating data inconsistencies and doubling data entry effort. (4) Single point of failure: one person in the company (the operations manager, who had built the database 15 years ago) understood the VBA code, the query structure, and the form design. 23 VBA modules containing 8,400 lines of code — undocumented, uncommented, and understood by one person. The operations manager: planning to retire in 18 months. His departure would leave the company unable to modify, fix, or even understand its core business system. (5) Integration isolation: the Access database couldn't connect to modern recruitment tools — LinkedIn Recruiter, job boards (Sapo Emprego, Net-Empregos, Indeed), email marketing (Mailchimp), or the company's website. All integrations: manual. A new candidate applying on the website: their information printed and re-typed into Access. A job posted on Net-Empregos: manually entered on the job board, then manually entered in Access. Candidate emails: sent through Outlook with no connection to the candidate's Access record.
We built a modern recruitment management application over 12 weeks, migrating all data from Access. (1) Application architecture: Next.js web application (accessible from any browser — office, home, mobile) with Node.js API and PostgreSQL database. The application: replicating all Access functionality while adding modern capabilities. Candidate management: candidate profiles with full history (applications, interviews, placements, communications), advanced search (full-text search across CV content, skills, experience, location — results in milliseconds vs. 15-30 seconds in Access), and candidate pipeline (visual kanban board showing candidates progressing through stages — sourced → contacted → interviewed → offered → placed). Company management: company profiles with contact details, open positions, placement history, and billing information. Relationship tracking: which consultant manages which company relationship, with communication history visible to the team. Position management: open positions linked to companies, with candidate matching (the system suggesting candidates based on skills, experience, and location match), job board distribution (posting a position to Net-Empregos, Indeed, and the company website from one form — the API handling distribution to each platform), and LinkedIn Recruiter integration (candidate profiles linked to LinkedIn profiles, InMail history visible alongside other communication). Placement and billing: placement records linking candidates to positions, with billing milestones (invoice on placement, invoice on probation completion), automatic invoice generation (integrated with the company's invoicing system for AT e-fatura compliance), and commission calculation (consultant commission calculated automatically based on the placement fee and the company's commission structure). (2) Data migration: all 42,000 candidate records, 8,500 company records, and 23,000 placement records migrated from Access to PostgreSQL. Migration process: Access tables exported to CSV, transformed via Node.js migration scripts (handling Portuguese character encoding — converting from Windows-1252 to UTF-8, normalising date formats, deduplicating records where Access's lack of constraints had allowed duplicates), loaded into PostgreSQL with referential integrity constraints. Data verification: automated comparison — record counts matching between Access and PostgreSQL for every table. Random sample of 500 records manually verified by the operations manager — confirming that data appeared correctly in the new application. Communication history: 180,000+ email records migrated from Access (the database storing email content as long text fields) — converted to a structured communication table with proper indexing for search. (3) VBA business logic migration: the 8,400 lines of VBA code analysed and reimplemented in TypeScript (Node.js API). Key business logic preserved: candidate matching algorithm (the operations manager's matching logic — weighting skills, experience, location, and salary expectations — reimplemented and validated against Access results. 200 test cases: modern system producing identical matches to Access in 198 cases, with 2 cases where the modern system was demonstrably more accurate due to data quality improvements), commission calculation (complex commission rules — sliding scale based on placement fee, team bonuses, and quarterly targets — reimplemented with unit tests verifying every rule), and billing rules (different billing structures per client — percentage of salary, flat fee, retainer — implemented as configurable billing templates rather than hard-coded VBA logic). Knowledge transfer: the operations manager spent 2 weeks working with our team during VBA analysis — explaining the business logic behind the code, identifying which VBA modules were actively used vs. abandoned, and validating the reimplementation. His institutional knowledge: captured in the application's business logic and documented for future developers. (4) Integration setup: LinkedIn Recruiter (API integration for candidate profile matching and InMail tracking), job boards (Net-Empregos, Indeed, Sapo Emprego — API integration for job posting distribution and application capture), email (Microsoft 365 integration — emails sent and received within the application, automatically linked to candidate and company records), and website (careers page on the company website automatically displaying open positions from the application, with applications flowing directly into the candidate pipeline). (5) Reporting: all Access reports reimplemented in the modern application. Monthly billing report: from 4 minutes (Access) to 3 seconds (PostgreSQL with proper indexing). Consultant performance dashboard: real-time visibility into placements, revenue, and pipeline — replacing the monthly Excel report the operations manager compiled manually. Client reports: automated monthly reports sent to clients showing position status, candidate pipeline, and placement activity.
Migration completed over 12 weeks — parallel running for 3 weeks, full cutover on week 13. Performance: candidate search from 15-30 seconds to under 1 second. Monthly billing report from 4 minutes to 3 seconds. Form loading: from 8 seconds to instant. The consultants: visibly more productive — less time waiting for the system, more time on recruitment activities. Multi-user access: zero record locking conflicts (PostgreSQL handling concurrent access properly — vs. 5-10 daily conflicts in Access). Zero database corruption (PostgreSQL's WAL — Write-Ahead Logging — providing crash recovery that Access lacked). The monthly "compact and repair" ritual: eliminated. Remote access: all consultants accessing the application from home, office, or mobile — the hybrid work constraint completely resolved. Mobile access: consultants checking candidate details and updating records from their phones during client meetings and candidate interviews. Data entry efficiency: eliminated double-entry from the spreadsheet workaround — saving approximately 30 minutes per consultant per day for the 60% working hybrid (13 consultants × 30 minutes × 120 days/year = 780 hours/year saved). Single point of failure: eliminated. The application code: in version control (Git), documented, and maintainable by any TypeScript developer. The operations manager: transitioning from system owner to system user — focusing on operations management rather than database maintenance. His retirement: no longer a business continuity risk. Integration value: LinkedIn integration reducing candidate sourcing time by 25% (consultants finding candidates within the application rather than switching between LinkedIn and Access). Job board distribution: posting time from 45 minutes per position (manual entry on each board) to 5 minutes (post once, distribute automatically). Application capture: candidates applying online flowing directly into the pipeline — eliminating print-and-retype workflow. Revenue impact: consultants spending approximately 45 minutes more per day on billable recruitment activities (time previously consumed by system slowness, data entry, and workarounds). At 45 consultants: approximately 500 additional billable hours per month. The company estimating that the productivity improvement contributed to a 12% increase in placements over 6 months — approximately EUR 228,000 in additional revenue. Development cost: EUR 48,000 (12-week project). Annual operating cost: EUR 3,600 (cloud hosting, database, email integration). Annual value: EUR 228,000 (estimated placement increase) + EUR 35,000 (time savings) + EUR 15,000 (eliminated Access licensing and workaround costs) = EUR 278,000. ROI: 5.8x in the first year.
Modernize one module at a time — reducing risk, delivering value early, and keeping the business running throughout.
We extract and document the business rules embedded in legacy code so nothing gets lost in the new system.
Migrate from legacy databases (Access, FoxPro, SQL Server) to modern PostgreSQL or cloud-managed databases.
Build modern REST or GraphQL APIs that let the new system talk to legacy components during the transition period.
Create comprehensive test suites that verify the new system behaves identically to the old one for every critical workflow.
Deploy the modernized application on AWS, Azure, or Vercel with CI/CD pipelines, monitoring, and auto-scaling.
Lisbon's legacy modernization market includes Portuguese IT companies (Novabase, Altice Labs, Accenture Portugal — capable of large modernization projects but expensive and often recommending enterprise platforms rather than custom development. Minimum engagement sizes that exclude SMEs), freelance developers (available in Lisbon — cost-effective for small migrations but lacking the methodology and risk management needed for complex modernization. The risk: a freelancer who underestimates the legacy system's complexity and delivers an incomplete replacement), offshore development (lower rates but legacy modernization requires deep understanding of the existing system — which is hard to communicate remotely. Portuguese business systems, Portuguese regulatory requirements, and Portuguese language data: additional complexity for offshore teams), and low-code platforms (OutSystems — a Portuguese company — offering rapid application development. Effective for simple replacements but limited for complex business logic, and creating vendor lock-in). ZTABS provides legacy modernization with a risk-managed methodology (thorough assessment, incremental migration, parallel running), Portuguese business system expertise (Primavera, PHC, AT integration), and modern technology (Next.js, PostgreSQL — not replacing legacy with another soon-to-be-legacy platform).
Legacy modernization in Lisbon ranges from EUR 15,000-35,000 for Access-to-web migrations (single database, basic forms, standard reporting) to EUR 50,000-150,000 for enterprise application modernization (complex business logic, multiple integrations, large data migration). Assessment and planning: EUR 3,000-8,000 (standalone — credited against development if proceeding). ZTABS provides fixed-price phases with clear deliverables and rollback capability at each phase.
Verified reviews from real client engagements — sourced from our public testimonial archive and Clutch profile.
My experience is throughout positive. Communication, service, the short response times and the flawless execution of a challenging topic was absolutely great. ZTABS is definitely my first choice again.
Christian Neff
Bank Software Advisory · Bank Software Advisory
Fintech
Fantastic Agency! I couldn't fault them even if I tried. They always go above and beyond to meet your expectations and always produces quality work. Thank you ZTABS.
Stephanie Kal
CEO · Beauty Finder Australia
Marketplace
It has been great working with ZTABS. They bounce off the ideas along the way. Amazing Experience.
Joel Rowe
CEO · Drill Quoter
Marketplace
We don't just contract — we ship and operate our own software. 17 products in production.
Common questions about legacy app modernization for Lisbon businesses
Yes — Access database modernization is one of our most common Lisbon projects. We migrate the data to PostgreSQL, rebuild the forms as a web application (Next.js), and reimplement the VBA logic in TypeScript. The result: accessible from any browser, multi-user without conflicts, no size limits, and maintainable by any modern developer. Typical timeline: 8-12 weeks.
ZTABS is a remote-first legacy app modernization agency serving Houston businesses — including incremental modernization, business logic preservation, data migration. We work with Energy & Oil/Gas, Healthcare & Biotech, Aerospace & Defense companies in Houston, TX via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Legacy App Modernization in New York, NYZTABS is a remote-first legacy app modernization agency serving New York businesses — including incremental modernization, business logic preservation, data migration. We work with Finance & Fintech, Media & Advertising, Fashion & Retail companies in New York, NY via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Legacy App Modernization in Los Angeles, CAZTABS is a remote-first legacy app modernization agency serving Los Angeles businesses — including incremental modernization, business logic preservation, data migration. We work with Entertainment & Media, E-commerce & DTC Brands, Gaming & AR/VR companies in Los Angeles, CA via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Web Development in Lisbon, PortugalZTABS is a remote-first web development agency serving Lisbon businesses — including full-stack development, progressive web apps, api development. We work with Tourism Tech, FinTech, PropTech companies in Lisbon, Portugal via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Web Design in Lisbon, PortugalZTABS is a remote-first web design agency serving Lisbon businesses — including ui/ux design, responsive design, custom interfaces. We work with Tourism Tech, FinTech, PropTech companies in Lisbon, Portugal via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
AI Development in Lisbon, PortugalZTABS is a remote-first AI development agency serving Lisbon businesses — including llm integration & fine-tuning, ai agents & automation, rag & knowledge systems. We work with Tourism Tech, FinTech, PropTech companies in Lisbon, Portugal via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Legacy App ModernizationLearn more about our legacy app modernization services nationwide.
Partner with ZTABS for expert legacy app modernization in Lisbon. Get a free consultation today.
