Region Conversion

Imported your Mercedes from the US, Japan, China, or the Gulf and now nothing matches the local cars? Speedometer stuck in MPH, headlights failing the inspection, ambient lighting missing zones, MBUX refusing to learn your language, navigation map covering the wrong continent? That's a region conversion job.

Region conversion is coding-first, map-licence-second, and hardware-third. Most imports only need the coding and map layers done. Some chassis also need physical part swaps - we'll tell you up front which bucket your VIN falls into.

What gets converted

Depending on direction (US → EU, EU → US, JP → EU, CN → EU, GCC → EU), the bundle includes some or all of:

• Instrument cluster units (MPH ↔ KPH, °F ↔ °C, gallons ↔ litres)
• Speedometer primary scale
• Headlight beam pattern (EU asymmetric ↔ US SAE)
• Daytime running lights
• Side marker lights & reflectors
• Turn signal colour / flash rate
• Rear fog lamp
• MBUX language packs & keyboard
• Navigation map region
• Radio bands (HD Radio / DAB+ / SiriusXM)
• TPMS threshold & units
• eCall / emergency call
• Clock format & date format
• Tyre sizing & consumption display
• Cluster badging

US → EU (the most common job)

• Cluster units to metric, KPH primary
• Headlight beam to EU asymmetric
• Side markers off
• Rear fog enabled
• Turn-signal colours corrected
• DRL to EU behaviour
• MBUX language packs + keyboard + voice locales
• Navigation map swapped from NAR to EU - generate the map licence here
• HD Radio off, DAB+ on
• eCall where hardware present

Newer cars (W206, W223, X254, EQE, EQS) need SECoC commissioning - we handle it.

EU → US / Canada

• Cluster to imperial, MPH primary
• Headlight beam to SAE
• Side markers + DRL to US pattern
• Nav map to NAR
• HD Radio on, DAB+ off, SiriusXM where supported
• Cluster badging and language defaults

FMVSS compliance is the owner's / shipper's responsibility. We code software to factory-US spec; we don't certify the car for the DOT.

JP → EU / ROW

• Cluster speed-limit + map speed units
• EU map region + map licence
• Language packs, keyboard, voice locale
• Headlight beam pattern
• DAB+ enable where hardware present
• DSRC / ETC module deactivation

CN → EU / ROW

• EU map licence + language pack
• Baidu / China-specific MBUX apps removed
• CN telematics stack deactivated
• Head-unit swap where model year requires it

Send the VIN - some CN chassis convert cleanly, some need a head-unit swap.

GCC → EU

• DAB+ enable
• EU locale defaults
• Map region swap

Map region changes in detail

The navigation map is its own transaction, separate from coding:

1. We identify your NTG / MBUX generation and confirm the required map version.
2. You buy the correct region disc, USB, or SD card (EU map, NAR map, JP map, etc.).
3. We generate the map licence tied to your VIN via the map code flow. Works on NTG4, NTG4.5, NTG4.7, NTG5, NTG5.5, NTG6, NTG7 / MBUX Gen 2 where Mercedes still publishes map updates.
4. Coding switches the head-unit's active map region so the correct hemisphere loads on boot.
5. On MBUX Gen 2 (NTG7 / Zero-Layer) the head-unit re-downloads the address database and rebuilds the search index on first boot after the swap.

If you already have the media, the whole map region change is a single session. If you need the media plus licence plus coding, we handle it end to end.

Hardware you might still need

Region conversion is software-first, but some jobs still need parts. We'll tell you which before you commit:

• Headlamp assemblies - on halogen / early xenon cars where the beam pattern isn't a coded parameter.
• Rear fog lamp - if the US-spec bumper skipped the fog housing entirely.
• DAB+ antenna + tuner - on pre-2018 cars that didn't ship with DAB from the factory.
• Telematics swap - some China-spec cars need an EU TCU for eCall and over-the-air updates to work.
• TPMS valves / sensors - regional frequency differences on a handful of older chassis.

Most imports (2015+) only need coding and map work. The hardware list gets shorter every model year.

What we need from you

To quote a region conversion, send:

• The VIN - we pull the SA codes and tell you exactly what's reachable in coding vs. what needs parts.
• The destination market (EU, UK, CH, NO, NA, etc. - map sets and eCall differ).
• Your preferred languages for MBUX, voice, and keyboard.
• Whether you already have the target map media, or need us to source it.
• Whether the car will be inspected soon (MOT, TÜV, control technique, ITV, RDW, etc.) - some items are inspection-blockers and we'll prioritise those.

How a session runs

• Remote for everything that's coding + map + language. Your Windows laptop, our bench, an ENET cable on your side. The VCI guide walks through the cable pick.
• Workshop partner if hardware swaps are in the mix - we line up a shop near you for the mechanical side and run the coding remotely into their laptop.
• On-site for partner workshops in our region, by appointment.

Typical end-to-end conversion is 2 to 4 hours of active session time, spread across one or two sittings. Map downloads on Gen20x cars add standalone time but don't need us on the line.

Pricing

Region conversion pricing is VIN-specific. The SA codes, target market, map licence, and whether any hardware has to ship all move the number. We don't publish a flat rate because we've seen the same model year need anywhere from a 90-minute session to a full day plus parts.

Contact us for a quote with your VIN and destination market. We reply the same working day on weekdays with:

• A line-by-line list of what's converting (coding, map, hardware).
• A fixed price for the coding + map side.
• A separate parts estimate if anything mechanical is in the mix.
• Expected session time.

No charge to scope the job, and no charge if the conversion isn't feasible on your VIN.

FAQ

Is this legal?

Coding side, yes - we write factory variants your chassis supports, nothing custom. Hardware side is your importer's job (FMVSS, EU type approval, national homologation). We don't sign off on road-legality - we make the car match the destination market's factory spec.

Will it break OTA updates?

No. Once the region is set, Mercedes' OTA pipeline sees the car as a native EU / NA / whatever car and pushes the matching firmware.

Will my US warranty stay valid?

If you're asking this, the warranty probably already ended when you exported the car. On in-warranty imports, Mercedes USA won't honour claims on a car coded to EU spec - and vice versa. Dealers can re-flash the region if needed.

Can I convert back later?

Yes, every direction is reversible in coding. Map licences are tied to the VIN, so the target map stays usable. Hardware that was swapped stays swapped until you put the original parts back.

Does this work on a W204 / W221 / pre-2011 car?

Often yes, with caveats. NTG2 and NTG3 maps are harder to source, some units stopped getting licences years ago. Send the VIN and we'll check.

Related reading

• Vehicle coding overview - pricing bands, DIY vs. remote, the full picture.
• VCI / OBD cable picker - which interface your chassis needs.
• Star3 SECoC coding - what's happening under the hood on Gen20x cars.
• Remote Diagnosis - if the import is throwing faults, start here.
• Map code generator - generate the licence for the new map region.
• Coding landing page - real footage of what ships on the cars we touch.

Contact

Email contact@mbretrofit.it with subject line Region conversion request and include your VIN + destination market. Same-day reply on weekdays.