Localizing a Global CRM for the Turkish Market

Localizing a Global CRM for the Turkish Market

A global CRM rolled into Turkey unchanged fails in a predictable place, and it is not the language setting. It is the consent field. Marketing permission in Turkey is not a boolean your system owns. It is a state held in a national registry, the İleti Yönetim Sistemi (İYS), and your CRM has to stay in step with it. Under the Regulation on Commercial Communication and Commercial Electronic Messages, consents obtained outside İYS must be recorded there by the service provider within three business days (Article 7(11)), consents not recorded in İYS are deemed invalid (Article 7(12)), and sending commercial electronic messages to recipients with no consent recorded in İYS is barred (Article 5(3)).

A checkbox labelled “marketing opt-in” cannot carry that. What the system needs is per-channel permission with timestamps, evidence of how it was obtained, and an integration that keeps both directions synchronised — because opt-outs run on the same three-business-day clock. This article covers the consent layer, the identity and address fields that break imported data models, currency handling in an inflationary market, where the data is allowed to live, and the integrations that decide whether the CRM is usable at all.

Table of Contents

What localizing a CRM actually means

Brands tend to treat CRM localisation as a translation project with a tax field attached. It is four separate layers, and only the first is translation.

Layer What it covers Who usually owns it
Interface Menus, labels, help text in Turkish for the people using the system daily IT, with the vendor
Data model Identity numbers, address structure, name fields, phone format, currency Nobody, until something breaks
Compliance Consent state, lawful basis, evidence, retention, transfer Legal, late
Integration İYS, messaging, invoicing, payment, marketplace orders Local team or implementation partner

The second and third layers are where market entries lose months. They are invisible during a demo, invisible during a pilot with twenty records, and unavoidable the first time the Turkish team tries to run a campaign or produce an invoice from a CRM record.

One framing that helps with the budget conversation: the interface layer makes the system pleasant, the integration layer makes it useful, and the data and compliance layers make it lawful. A project funded only for the first is a project that will be redone.

In most markets the CRM is the system of record for marketing permission. In Turkey it is a mirror of a national registry, and the difference changes the data model.

What the Regulation requires, and what each requirement implies for the system:

  • Senders must be registered with İYS (Article 5(2)), and messages may not be sent where no consent is recorded there (Article 5(3)). The CRM’s send logic therefore cannot rely on its own field alone.
  • Consents taken outside İYS must be recorded within three business days (Article 7(11)). A nightly or weekly batch is the design that fits; a manual monthly export is not.
  • Consents not recorded in İYS are invalid (Article 7(12)). A permission sitting in your CRM that never reached the registry is not a permission.
  • Opt-outs run on the same clock. Refusals received by the provider are reported to İYS within three business days (Article 9(6)), and sending must stop within three business days of the request (Article 10(1)).

Four fields that an imported CRM almost never has, and needs:

Permission per channel, not per contact. Email, SMS and call are separate permissions and have to be stored and synchronised separately.

Source and evidence of the permission. Which form, which wording, which page, which date. A consent you cannot evidence is one you cannot defend.

Registry state and last sync time. Distinct from your own field, so the team can see when the two disagree — which they will, because consumers can also opt out directly through İYS.

Lawful basis, where consent is not the basis. Not every processing activity runs on consent, and a system that records only an opt-in flag cannot express that.

One further design point that is frequently got wrong at the form end rather than in the CRM: the privacy notice and explicit consent are separate acts. In its decision numbered 2018/90 of 26 July 2018, the Personal Data Protection Board held that fulfilling the obligation to inform and obtaining explicit consent must be carried out separately, and instructed the controller to separate the mechanisms evidencing each. A CRM field that records “accepted terms and consented” as one event is recording something the Board has treated as two. The form side of this is covered in our guide to campaign landing pages for Turkey, and the wider framework in our guide to KVKK compliance for foreign brands marketing in Turkey.

Identity and tax fields

Turkish commercial records are organised around identifiers your global schema does not have, and bolting them into a free-text “VAT number” field creates problems downstream in invoicing.

The two that matter:

  • T.C. Kimlik Numarası (TCKN) — the 11-digit national identity number held by Turkish citizens, which also serves as their tax identification number.
  • Vergi Kimlik Numarası (VKN) — the 10-digit tax identification number assigned by the Revenue Administration (Gelir İdaresi Başkanlığı), used by legal entities, and by foreign nationals who do not hold a TCKN.

Four implications for the data model. The two identifiers have different lengths and different validation, so a single field with one format rule will reject valid records. A B2C record and a B2B record carry different identifiers, which means the customer type has to be a structured field rather than an inference. The tax office (vergi dairesi) is a separate field that invoicing needs and that marketing systems usually omit. And an identity number is sensitive data in practice even where it is not formally special-category: it should be collected only where there is a genuine need, not captured by default because the field exists.

Confirm the exact format and validation requirements with your Turkish finance or tax adviser before building the rules, particularly where the CRM feeds an invoicing system.

Names, addresses and the dotted i

Three structural mismatches account for most of the data quality damage in a localised CRM, and the third is the one nobody predicts.

Names. Turkish names are given name plus family name, with no middle name convention. A schema with a required middle name field produces junk; a single “full name” field makes salutations and deduplication harder. Two fields, neither required to be anything they are not, is the workable answer.

Addresses. Turkish addresses run from the largest unit down — province (il), district (ilçe), neighbourhood (mahalle), then street and building — and the postal code plays a far smaller identifying role than in the United Kingdom or Germany. A schema built around a postcode lookup will produce addresses that validate and cannot be delivered to. Province and district should be controlled lists rather than free text, because reporting and territory assignment depend on them. The checkout-side version of this problem is covered in our guide to payment methods and checkout localization for Turkey.

The dotted and dotless i. Turkish distinguishes four letters where English has two: i and İ, ı and I. Case conversion is therefore locale-dependent — uppercasing “i” gives “İ” in Turkish and “I” in English, and lowercasing “I” gives “ı” in Turkish and “i” in English. Any system that normalises text by changing case with the wrong locale will fail to match records that are in fact the same person, and may match records that are not. This affects search, deduplication, sorting and email-address normalisation, and it is a silent failure: nothing errors, the duplicates simply accumulate. Specify the locale explicitly in the matching and sorting rules rather than relying on a default.

Phone numbers. Store in a normalised international format with the +90 country code, and accept the local formats people actually type. A field that rejects a correctly entered Turkish mobile number loses the record and the lead with it.

Currency and price in an inflationary market

A CRM holding prices in a market where they are revised frequently has to answer a question most global configurations do not: as of when.

Store the currency with every monetary value, and store the rate and date where a conversion was applied. A deal value recorded as a bare number is uninterpretable six months later.

Version the price list rather than overwriting it. Quotations issued last quarter were correct at the time, and reporting that silently reprices them is reporting fiction.

Decide which currency the pipeline is managed in — and report both. A pipeline held in lira and a target set in euros will diverge for reasons that have nothing to do with sales performance.

Set quotation validity periods deliberately. An open-ended quotation is a commercial exposure in this market, and the validity window belongs in the CRM’s template rather than in the salesperson’s judgement. The pricing logic behind these choices is covered in our guide to pricing strategy in Turkey, and the field-facing side in our guide to digital sales presentations for field teams in Turkey.

One formatting detail that causes real confusion in exports and imports: Turkish number formatting uses a comma as the decimal separator and a dot as the thousands separator. A CSV round-trip between a Turkish spreadsheet and an English-locale system is a known source of silently corrupted values.

Where the data is allowed to live

Most global CRMs are hosted outside Turkey, which makes the Turkish team’s everyday data entry a cross-border transfer. This is an obligation to satisfy rather than a reason to change platform, but it has to be settled before rollout.

Transfers abroad fall under Article 9 of Law No. 6698 as amended by Law No. 7499. The Personal Data Protection Authority’s guide on international transfers, published as KVKK Yayınları No: 48 in January 2025, sets out the regime: first an adequacy decision; failing that, appropriate safeguards — standard contracts, binding corporate rules, written undertakings, or agreements between public bodies; and only then narrow occasional exceptions, which the guide describes as transfers happening once or a few times rather than continuously. Where a standard contract is used, the Authority must be notified within five business days of the signatures being completed.

Two consequences specific to a CRM. Daily entry by a Turkish team into a system hosted abroad is continuous by design, so the occasional-exception route is not available to it. And the transfer analysis has to cover the whole chain, not just the CRM: the analytics tool, the support desk, the email platform and any backup location are each transfers in their own right. Take Turkish advice on which mechanism fits your architecture before the rollout rather than after.

Integrations that decide whether it gets used

A localised CRM that does not connect to the systems the Turkish business actually runs on becomes a reporting obligation, and adoption collapses accordingly.

İYS. The non-negotiable one, for the reasons set out above. Build it as a two-way synchronisation with a visible state, not a one-way export.

WhatsApp. A large share of Turkish commercial conversation happens there, and a CRM with no record of it is missing the customer history, as covered in our guide to WhatsApp Business marketing in Turkey.

Invoicing. Turkish electronic invoicing is handled through the Revenue Administration’s systems and the integrators that connect to them. The CRM does not have to issue invoices, but its customer records have to carry the fields invoicing needs — which is the practical reason the identity and tax office fields above matter.

Email and messaging platforms. With the consent state flowing correctly, not merely the contact list, as covered in our guide to email marketing in Turkey.

Marketplace and e-commerce order data. Where a meaningful share of sales comes through marketplaces, a CRM that cannot see those customers is describing a fraction of the business.

Partner systems. Where dealers hold the customer relationship, what flows between their systems and yours is both an integration question and a controller-role question, as covered in our guide to dealer and distributor portals in Turkey.

Medyae’s CRM and mobile application service covers this integration layer — custom CRM work and connection into existing systems and workflows — alongside the interface and application side.

Migration and deduplication

Most Turkish CRM rollouts are not greenfield. There is a spreadsheet, a distributor’s database, or an inherited system, and what comes across determines the first year of data quality.

Four checks before importing anything:

  • Does the legacy data have a lawful basis for this use? A list collected for order fulfilment does not automatically carry permission for marketing, and importing it into a marketing system does not create one.
  • Which contacts have İYS-registered consent? This is a different question from which contacts are marked as opted in, and the gap is usually larger than expected.
  • Is deduplication locale-aware? For the dotted-i reasons above, naive case-insensitive matching on Turkish names and email addresses produces both missed duplicates and false merges.
  • What is the retention position? Importing a decade of dormant records creates obligations without creating value. Decide what not to migrate, and document why.

One sequencing recommendation: migrate the records you can evidence consent for first and run the campaign programme on those, rather than importing everything and resolving the consent state afterwards under time pressure.

Who owns the configuration

A localised CRM diverges from the global template, and without an owner that divergence becomes either a frozen system nobody can change or a fork nobody can upgrade.

Name a local administrator with real permissions. Someone in Turkey who can add a field, change a validation rule and fix a price list without a ticket to another time zone.

Agree what is global and what is local. Reporting structure and core objects are usually global; consent fields, address structure, identity fields, price lists and templates are local. Writing this down prevents the two most common outcomes — a global release that silently breaks a Turkish validation rule, or a local change that breaks consolidated reporting.

Keep the Turkish configuration documented in Turkish and English. It is read by the local team and by the global system owner, and a configuration only one of them understands is one that cannot be maintained.

Decide who answers data subject requests. Access, correction and deletion requests arrive in Turkish and are time-bound. A process that routes them to a global privacy team without a Turkish-speaking first step is a process that will miss them.

Reporting consistency between the CRM and the marketing side is a related governance question rather than a technical one, covered in our guide to GA4 and marketing analytics setup for Turkey.

Common mistakes

  • Treating marketing consent as a CRM field. Article 7(12) makes a permission that never reached İYS invalid.
  • One opt-in flag for all channels. Email, SMS and call are separate permissions.
  • Manual İYS uploads. The three-business-day window in Article 7(11) does not fit a monthly export.
  • Forgetting the opt-out direction. Refusals have their own three-business-day obligations under Articles 9(6) and 10(1).
  • One validation rule for TCKN and VKN. Different lengths, different holders, different use.
  • Postcode-first address schema. It produces addresses that validate and cannot be delivered to.
  • Locale-blind case handling. The dotted and dotless i silently breaks matching and deduplication.
  • Storing monetary values without currency and date. Unreadable within months in this market.
  • Leaving the transfer question to go-live. Daily entry into a system hosted abroad is a continuous transfer under Article 9.
  • No local administrator. The configuration freezes or forks.

Frequently asked questions

Can our CRM hold marketing consent for Turkey on its own?

Not as the authoritative record. Under the Regulation on Commercial Communication and Commercial Electronic Messages, senders must be registered with İYS (Article 5(2)), messages may not be sent where no consent is recorded there (Article 5(3)), consents obtained outside İYS must be recorded within three business days (Article 7(11)), and consents not recorded are deemed invalid (Article 7(12)). The CRM should hold per-channel permission with evidence and a synchronised registry state, not a single opt-in flag.

Do we have to host our CRM in Turkey?

There is no general requirement to do so, but hosting abroad makes everyday entry by a Turkish team a cross-border transfer under Article 9 of Law No. 6698 as amended by Law No. 7499. The Authority’s guide, KVKK Yayınları No: 48 of January 2025, sets out adequacy decisions, then appropriate safeguards such as standard contracts, binding corporate rules or written undertakings, and only narrow occasional exceptions — which the guide describes as transfers happening once or a few times rather than continuously, so they do not cover daily use. Where a standard contract is used, the Authority must be notified within five business days of signature. Take Turkish advice on the mechanism that fits your architecture.

What fields does a Turkish CRM need that a European one does not?

Per-channel marketing permission with İYS state and sync time; the lawful basis where consent is not the basis; TCKN for individuals and VKN for legal entities, with separate validation; the tax office (vergi dairesi) where the record feeds invoicing; province, district and neighbourhood as structured address fields rather than a postcode lookup; and currency plus conversion date on every monetary value.

Why do duplicate records keep appearing in our Turkish data?

Frequently because of locale-dependent case conversion. Turkish distinguishes i/İ and ı/I, so uppercasing or lowercasing text with an English locale maps those letters differently and matching fails silently — the system does not error, the duplicates simply accumulate. Specify the Turkish locale explicitly in matching, sorting and normalisation rules, and re-run deduplication afterwards.

Should we localize the CRM or wait until volumes justify it?

The compliance layer does not wait for volume: consent obligations apply from the first message sent and the transfer question applies from the first record entered. The interface and integration layers can be phased. A workable sequence is consent and identity fields first, integrations next, interface and reporting refinements last.

Conclusion

Localising a CRM for Turkey is a data and compliance project with a translation component, not the other way round, and the sequence matters more than the platform choice.

Four things to settle before rollout. Build the consent layer as a synchronised mirror of İYS with per-channel permission, evidence and both directions covered, because Article 7(12) makes an unregistered consent invalid and opt-outs carry their own three-business-day obligations. Model identity properly — TCKN and VKN are different lengths with different holders, and invoicing depends on getting them and the tax office field right. Fix the address and matching rules for Turkish, including explicit locale handling for the dotted and dotless i, which otherwise corrupts deduplication quietly. And settle the cross-border transfer mechanism before go-live, because a Turkish team entering records into a system hosted abroad is transferring data continuously.

Where the CRM feeds campaign automation, our guide to marketing automation platforms in Turkey is the companion piece, and our pillar guide to marketing in Turkey for foreign brands is the place to start.

This article is general information about CRM configuration, commercial messaging and personal data obligations in Turkey, and the provisions cited carry the article numbers and publication details given. It is not legal, tax or accounting advice. Identifier formats, invoicing requirements, consent obligations and cross-border transfer mechanisms are fact-specific and should be confirmed with qualified Turkish advisers for your own architecture.