1–2. Source inventory and data quality

List every source, owner, access method, volume, history window, and retention requirement. Measure completeness, format validity, duplicates, orphaned relations, and values requiring a business decision. Profile data using a safe copy and controlled access.

3–5. Fields, extensions, and history

For each field, record source, meaning, native target or custom field, transformation, default, validation, and omission decision. Plan attachments, comments, activities, and historical documents separately. Open Mercato supports custom fields and entities, but their model must be deliberately designed.

Evidence for this section:

6–7. Identity, permissions, and transformations

User mapping covers active and inactive accounts, roles, organizations, record ownership, and author history. Transformation rules should be versioned, deterministic, and report rejected data; do not silently “fix” production data without an approved rule.

8–9. Trials and reconciliation metrics

Run a repeatable trial migration on representative data. Compare counts, required-field completeness, relationships, attachments, history, operational or financial totals, and samples approved by process owners. Report differences by cause, not only a success percentage.

10–12. Parallel run, cutover, and rollback

Decide whether the process needs parallel running, a source freeze, or incremental synchronization. The cutover plan names order, window, owners, communication, stop conditions, and return path. After launch, repeat reconciliation and critical-flow tests before retiring the source.

13. Use the worksheet safely

Use the mapping worksheet for schema, decisions, and evidence references. Do not paste personal data, secrets, or production records into it. If exported, handle the file under the organization’s information-classification rules.

  1. 1

    Source inventory and ownership

    Record input, owner, output, acceptance evidence and rollback implication.

  2. 2

    Data quality assessment

    Record input, owner, output, acceptance evidence and rollback implication.

  3. 3

    Object and field mapping

    Record input, owner, output, acceptance evidence and rollback implication.

  4. 4

    Custom fields and historical records

    Record input, owner, output, acceptance evidence and rollback implication.

  5. 5

    Attachments and activity history

    Record input, owner, output, acceptance evidence and rollback implication.

  6. 6

    Identity and permissions mapping

    Record input, owner, output, acceptance evidence and rollback implication.

  7. 7

    Transformation and default rules

    Record input, owner, output, acceptance evidence and rollback implication.

  8. 8

    Trial migrations

    Record input, owner, output, acceptance evidence and rollback implication.

  9. 9

    Reconciliation measures

    Record input, owner, output, acceptance evidence and rollback implication.

  10. 10

    Parallel run or freeze strategy

    Record input, owner, output, acceptance evidence and rollback implication.

  11. 11

    Cutover and rollback

    Record input, owner, output, acceptance evidence and rollback implication.

  12. 12

    Post-cutover verification

    Record input, owner, output, acceptance evidence and rollback implication.

Method, assumptions and limitations

Reviewed 14 July 2026. Product facts were checked against both the public code at the cited repository revision and official documentation. Where documentation and code differ, this guide describes behavior supported by code. Interpretations and recommendations concern implementation work, not product guarantees.

This material is not a quote, audit, certification, or legal, tax, or accounting advice. Edition, enabled modules, configuration, custom code, infrastructure, data, third-party providers, and operating practices affect the outcome.

Primary source collections: code repository, documentation, public releases.

Submit a correction with the public source and the date checked.