Global Salesforce rollouts touch every aspect of the platform. The decision tree:
Languages:
- Enable Translation Workbench for all target languages from day one.
- Set users' Locale + Language on their User record. The combination drives label translation, date format, number format, and currency display.
- For dynamic content (record data) — use Custom Labels for any user-facing string in code/components, so they translate via the workbench too.
- Knowledge articles support translation workflow per language.
- Dashboard / report titles — these are translated via the workbench; the report data isn't.
Currencies:
- Decide single-currency vs multi-currency before any user goes live (multi-currency is irreversible).
- If multi-currency, enable Advanced Currency Management for accurate historical rate handling.
- Plan integration impact — every system writing currency values must specify the
CurrencyIsoCode.
Regions / data segregation:
- For data residency, decide whether you need separate orgs per region (EU vs US vs APAC orgs, federated by SSO and integration) or a single global org with sharing controlling access.
- Single global org is simpler if compliance allows. Multi-org is mandatory in highly regulated industries (financial services in some jurisdictions).
- For a single org, use Public Group + Sharing Rule patterns to limit cross-region visibility, plus regional Page Layouts and Lightning Record Pages for region-specific UX.
Time zones:
- Each user has a Time Zone setting on their User record. Salesforce displays records in the user's TZ by default.
- For audit and reporting that needs UTC, build formula fields that convert to UTC and use those for analysis.
Business Hours:
- Configure separate Business Hours records per region (NA Business Hours, EMEA Business Hours, APAC Business Hours).
- Reference these in escalation rules, SLA calculations, and Service Cloud routing.
Page Layouts and UX:
- Different regions may need different fields visible (e.g., GDPR-mandated consent fields for EMEA, US-specific compliance fields for US).
- Use Record Types by region or Profile-driven Page Layouts to differentiate.
Compliance:
- GDPR — data subject rights, right to be forgotten, consent tracking.
- CCPA — California-specific.
- APAC variations — country-specific data residency rules.
- Use Privacy Center and Data Classification to track regulated fields.
Deployment cadence:
- A global rollout is rarely big-bang. Phase by region: pilot one country, expand to one region, then wave-by-wave globally. Each phase reveals the next round of localisation issues.
Most under-estimated cost: the per-region Page Layout / Lightning Page maintenance and the ongoing translation work as new fields ship. Build a translation/UX-update cadence into your release process from day one.