Case Study
EPOC: from WordPress to a custom platform, in three languages
1,325 URLs with translated slugs, capture wired to RD Station and the AWS infrastructure — in a partnership spanning over 15 years.
The client
EPOC TECH builds retail automation software for bars, restaurants, food service and retail — POS, ERP, electronic order pads, table control, digital menus, KDS and integration with fiscal printers, scales and card terminals. The website is its main acquisition channel: pages by type of operation (bar, bistro, franchises, delivery), lead magnets, calculators and a blog with hundreds of articles. We have partnered with EPOC and Oz Technology for over 15 years.
What the project demanded
This was not a redesign: it was changing the foundation, taking the content into three languages and keeping the commercial operation running on it.
Content volume
Hundreds of pages across products, systems by segment, lead magnets, calculators and a blog with years of accumulated publishing.
Rankings already earned
The site had history on Google. Any platform change had to preserve URLs, redirect what moved and not drop what was already bringing visits.
Capture as a core function
The site exists to generate qualified contact. The forms had to keep feeding RD Station without a gap during the migration.
Reach in three languages
Content had to exist in Portuguese, English and Spanish — with its own address per language, not a URL parameter that Google treats as a duplicate page.
What we built
A custom .NET platform, with content migrated and SEO mapped before the first public visit.
Migration with SEO mapped
443 routes rebuilt — 300 blog articles and 143 institutional and product pages — with 16 301 redirects for anything that changed address and explicit control over what stays out of the index.
In-house content editor
The team edits copy, blocks and pages from the panel, with a change history. Publishing no longer depends on a deploy.
Qualified capture
Forms that record company, city, role, revenue band and buying stage, plus the originating page — sales receives the lead with context already attached.
RD Station integration
Every conversion is pushed to RD Station automatically, with a connection test and resend when the API fails. No lead is left sitting in the database.
Admin panel
Content, leads, integrations, users and an audit trail across 14 screens — who changed what, and when, is on record.
Configurable forms
Fields, labels and messages defined by configuration and translatable, with no code needed to create or adjust a form.
Three languages, with translated slugs
441 of the 443 routes have their own address in Portuguese, English and Spanish — atendimento/balcao, service/counter, atencion/mostrador — totalling 1,325 URLs, each with hreflang and x-default. This is not parameter-based translation: every language has its own URL.
AWS infrastructure
Application on EC2, database on RDS, files on S3 and delivery through SES, on our own Amazon infrastructure. Whoever builds it also answers for the server.
Ongoing maintenance and SEO
The site was not delivered and forgotten: fixes, evolution, content publishing and SEO work continue month after month, with rankings and conversions tracked.
Continuous maintenance and security
The platform does not sit still after launch: it gets updates, fixes for disclosed vulnerabilities and environment oversight as part of maintenance.
What is live
The fronts the platform supports today, from the application to the infrastructure.
What changed
Concrete outcomes of changing the foundation.
Content preserved and multiplied
All 443 pages went live with their address kept or redirected, and now exist in English and Spanish too — from a single-language site to 1,325 URLs across three.
Publishing without depending on us
EPOC's team edits content from the panel. What used to go through a ticket is now done by whoever writes it.
Leads with context in the CRM
Sales receives the contact already qualified and with its originating page, straight into RD Station, instead of a loose email.
One party accountable for the operation
Site, content, capture, servers and SEO sit with the same team. When something fails, there is no finger-pointing between the software vendor and the infrastructure vendor.
The number that matters here is 443: every page changed platform without a single address being lost — and the EPOC team was publishing from the panel the day after the switch.
What the client says
SuaEmpresa.Net has been a great partner to EPOC and Oz Technology over the years, building and supporting our website and running our digital campaigns. We have worked together for more than 15 years and have always seen a genuine interest in helping us improve our exposure to the market.
The services in this project
The same work we do for other companies.
Need to change platform without losing rankings?
Migration with mapped URLs and planned redirects is what stops you losing what you already earned. Tell us your case.