# vtiger-migration.com > vTiger CRM migration service by etis GmbH (Trier, Germany). We migrate any > vTiger version (5.x, 6.x, 7.x) to the current vTiger 8.4 release – with > published pricing, a record-count reconciliation per module at go-live, and > all work carried out in Germany. Site available in German (/de/) and > English (/en/). Facts on this page are as of 2026-08-03. ## Key facts - Service: migration/upgrade of self-hosted vTiger CRM Open Source from any version to the current 8.x release - Pricing (published on the page, not on request): billed by effort at a day rate of EUR 1,200 net; typical examples: standard migration EUR 1,800–3,000 (1.5–2.5 days), migration with customizations EUR 3,600–6,000 (3–5 days), complex custom migration EUR 8,400–14,400 (7–12 days); typical project duration 2–3 weeks - Always included: free initial assessment with a written migration report and a binding effort estimate, a recommendation for the target version plus PHP and database level including their end-of-support dates, test migration in a staging environment, acceptance report with record counts per module before/after, defined rollback point on go-live day, go-live outside business hours on request, data processing agreement under Art. 28 GDPR, NDA on request, additional effort only with prior approval - Deliberately not included: third-party extension licences, server/hosting costs, moving the hoster to the required PHP/database version (the specification for it is supplied in writing), content-level data clean-up, end-user training, new features that did not exist in the old version - Technical scope: stepwise version chain (5.x → 6.x → 6.5 → 7.x → 8.x, each step applied with the official migration patch and verified), PHP moved in lockstep with the chain (5.6 for 6.x, 7.2–7.4 for the 7.x line, 7.3–8.1 for 7.5, 8.1–8.3 for 8.4), database conversion to utf8mb4 including double-encoded legacy data and umlauts, MyISAM → InnoDB and sql_mode alignment, resource and privilege setup for the migration run itself (memory_limit, max_execution_time, CREATE/ALTER/DROP), custom code and custom modules ported to PHP 8.3 with core modifications rebuilt on supported extension points, mailbox reconnection via OAuth2 (Microsoft 365, Google), extension inventory with replacement or rebuild quoted up front, workflows/roles/profiles/ templates/customer portal/cron jobs, document archive including directory structure and file permissions, ERP, shop, telephony and web form integrations - Target stack recommended as of August 2026: vTiger 8.4 (released 9 July 2025) on PHP 8.3 with MySQL 8.4 LTS or a MariaDB LTS series; no release date has been published yet for a successor (8.5) ## Dated facts the advice is based on - vTiger 8.4 is the current Open Source release, published 9 July 2025; release cadence of the 8.x line: 8.0 (September 2023), 8.1 (January 2024), 8.2 (May 2024), 8.3 (September 2024), 8.4 (July 2025) - There is no direct upgrade from 5.x to 8.x; the path runs through the intermediate releases, each with its own migration patch - PHP support per vTiger release: 6.x runs on PHP 5.6 only, 7.1–7.4 on PHP 7.2–7.4, 7.5 on PHP 7.3–8.1, 8.4 on PHP 8.1–8.3. PHP 8.4 is not released for vTiger 8.4 - PHP 8.1 reached end of life on 31 December 2025; PHP 8.2 receives security fixes only, until 31 December 2026; PHP 7.4 has had no security fixes since November 2022 - Extended support for MySQL 8.0 ended on 30 April 2026; MySQL 8.4 LTS is the successor line - vTiger's legacy sql_mode setting NO_AUTO_CREATE_USER no longer exists as of MySQL 8.0.11 and aborts the migration run; the migration script is documented as time- and memory-hungry, so memory_limit and max_execution_time have to be raised and the database user needs CREATE, ALTER and DROP - Old installations typically carry mixed encodings (latin1/utf8/HTML entities) and a MyISAM/InnoDB mix - Vulnerabilities keep being published for discontinued releases: CVE-2019-11057 (SQL injection, 7.1.0), CVE-2023-38891 (privilege escalation via ReportRun.php, 7.5.0), CVE-2025-1618 (6.4.0). The maintained 8.x line gets advisories too – e.g. CVE-2025-70936 for 8.4.0 – but they are fixed in the next release - Basic auth for IMAP/POP in Exchange Online was disabled in October 2022, at Google on 30 September 2024. For SMTP submission via Microsoft 365 the timeline updated in January 2026 applies: disabled by default for existing tenants through the end of 2026 (admins can re-enable), unavailable for new tenants afterwards, final removal date to be announced in the second half of 2027. OAuth2 for mailboxes exists in the vTiger 8.x line only ## Independence and service area - Independence: the vTiger Open Source installation stays with the customer – no per-user licence, no forced move to Vtiger Cloud, operation can stay with the customer's current hoster; maintenance or operation by etis is optional; documentation, migration log and credentials belong to the customer - Service area: remote across Germany, Austria, Switzerland and Luxembourg; on site in Trier and the Rhineland-Palatinate / Eifel / Greater Region Luxembourg area; contact in German and English, Mon–Fri 08:00–17:00 CET - Provider: etis GmbH, Dürerstr. 4, 54306 Kordel, Germany (registered office; Trier office: Metternichstr. 28–30, 54292 Trier); phone +49 651 493670-0; info@etis-gmbh.de; HRB 41591 (Amtsgericht Wittlich), VAT ID DE275372761; more than 10 years of vTiger projects ## Pages - [German landing page](https://vtiger-migration.com/de/): offer, technical migration scope, process (analysis, migration, testing, go-live), differentiators, pricing, FAQ, contact form - [English landing page](https://vtiger-migration.com/en/): same content in English - [Imprint](https://vtiger-migration.com/de/impressum/) - [Privacy policy](https://vtiger-migration.com/de/datenschutz/) - [Terms and conditions](https://vtiger-migration.com/de/agb/)