// proof
The site comes back up and looks fine. A week later one market has been quoting the wrong tax, or half a catalogue stopped showing in one country. That is why we start with a compatibility audit and test every store view separately — not just the default one.
Central European rates, an EU timezone that overlaps your working day, and the people doing the work on the call rather than an account manager between you and them. We run Magento day to day — Hyvä, B2B, multistore, ERP integrations. Being based in Poland is a pricing and timezone advantage, not a limitation.
Fixed at both stages. The audit is a flat EUR 450 and the build gets a single figure once the audit is done. Hourly, at EUR 45, applies only to work outside the agreed scope — and always against an estimate you approved beforehand, never after the fact.
Three routes, in this order: update to a compatible release if the vendor shipped one, replace it with an equivalent including data migration, or repair and rewrite it on our side. The audit says which route applies to which module and what it costs. The choice stays yours.
Yes, within an agreed window. In practice that means a database dump and a filesystem snapshot taken immediately before deployment. Be aware that after a point, orders placed on the new version start blocking a rollback — that is data consistency, not technique. We fix the length of that window in writing before go-live.
Those are yours and we count them during the audit. Moving to a build compatible with the new Magento line often needs an active vendor subscription — Amasty, Mageworx, Mirasvit and similar. It is a common nasty surprise mid-project, so we price it before anything starts.
Read-only SSH to production or a copy, composer.json and composer.lock, the output of bin/magento module:status and setup:db:status, a database schema dump (data is not needed and can be anonymised), repository access or an archive of app/code and app/design, server specifications and a list of external integrations.
Yes, and we treat it as a condition. We do not take on an upgrade quoted blind — that is the single most common reason these projects run fifty percent over budget. If you already have a recent audit from someone else, we will happily quote from it.
Check your Magento 2 store in ~30 seconds: exposed files, security headers, technical SEO and performance measured on real users. No login, nothing to install.
Run a free scan →Tell us which version you are on and where you want to get to. If you have composer.lock or the output of bin/magento module:status to hand, attach it — the answer gets far more specific.