Appearance
Process historical data after enabling multiple currencies
Understand default historical-data behavior and the boundary for special migrations when the multi-currency feature is enabled for an existing enterprise.
WARNING
A currency migration is not a general administrator operation that can be performed from this page alone. Do not update production data in bulk until the data scope, exchange-rate baseline, scheduled task, or special approval has been confirmed.
Default behavior
When an existing enterprise enables multiple currencies, historical records retain their existing state. Their currency fields are treated as the current enterprise base currency.
Boundary for special processing
If selected records must use another transaction currency, delivery or engineering can assess a scheduled data-synchronization task. Official documentation does not provide a universal field map or recalculation procedure. Validate the currency, rate, and base-currency amount with test data before production processing.
If the enterprise previously used a special design such as custom fields and wants to migrate to the standard platform capability, submit a special approval request and create a data-migration plan. Do not treat it as a standard enablement.
Choose a processing path
| Scenario | Processing method | Can an administrator run it directly? |
|---|---|---|
| Historical records remain in the base currency | Keep the default result and perform sample checks | Yes |
| Selected historical records need another transaction currency | Have delivery or engineering assess a scheduled task and validate test data first | No bulk execution |
| Migrate from an enterprise-built design to the standard capability | Submit special approval and define field mapping, rates, and rollback | No |
Prepare a processing request
- Export record identifiers, original amounts, original and target currencies, and business dates.
- Define the exchange-rate date or batch and whether base-currency amounts must be recalculated.
- Identify affected master-detail objects, calculated and summary fields, workflows, reports, and external integrations.
- Prepare repeatable samples, expected results, and rollback data.
- Obtain written confirmation of scope and conversion rules from the finance or business owner before submitting a scheduled-task or special-approval request.
Preproduction checks
- Define the historical-data scope and target currencies.
- Back up or export auditable samples.
- Validate with test data or a small record set.
- Check original- and base-currency results in details, lists, summaries, and reports.
- Expand processing only after the finance or business owner confirms the result.
If the result differs from expectations, stop expansion. Restore or correct the plan using the reference samples, then verify rate dates, master-detail currency inheritance, and reporting rules.
NOTE
The platform does not provide real-time exchange rates. External-rate integration can use OpenAPI, but the enterprise must design update frequency, historical-rate policy, and failure handling.