Step 6 of 11 · Implementation · Updated November 19, 2026

Sage X3 data mapping

Data mapping is where the business decisions of a Sage X3 migration are made. A mapping that copies the legacy structure one to one usually carries the legacy problems into Sage X3. superglue's agent proposes field mappings and transformations, you decide the ambiguous cases, and the client signs transformed files before anything loads.

How this step works

What the agent does

  • Proposes field mappings and value translations from the source structure to Sage X3.
  • Lists the ambiguous cases and the records that cannot map, with counts.
  • Builds a client questionnaire for questions only the client can answer.
  • Produces transformed files for review.

What you decide and approve

  • The business meaning of ambiguous fields and codes.
  • What happens to records that cannot map.
  • When the mapping is ready for the client's signature.

What the client gets

  • A mapping report to sign.
  • Transformed files to review before the load.

Key Sage X3 mapping decisions

  1. 01

    Customers and vendors to business partners

    Map each legacy customer and vendor to a business partner, and agree the merge rule for companies that appear in both lists.

  2. 02

    Legacy segments to accounts and dimensions

    Map each legacy segment to the account or to a dimension type. Dimension codes have at most 15 characters.

  3. 03

    Items to categories and product-sites

    Map each item to a product category, and each item at each site to a product-site record with its valuation method.

  4. 04

    One template per object

    The reference folder supplies an editable import template for each object that can be imported. An order and its customer cannot import together, so master data loads first.

Frequently asked questions

What are the key Sage X3 mapping decisions?

Customers and vendors to business partners; Legacy segments to accounts and dimensions; Items to categories and product-sites; One template per object. The agent proposes an answer from the source data, and you confirm or change it.

Can the client review the mapping before anything loads?

Yes. The agent produces transformed files and a mapping report. The client signs the mapping, and the load uses exactly the signed mapping.

How does superglue work with our consultants?

superglue works alongside your team. The agent takes on the repetitive work, such as reading documents, drafting, mapping, loading and reconciling. Your consultants keep the client relationship and the decisions, and they approve every change to a client system.

Can we use our own implementation method?

Yes. Write your firm's method as a playbook, and every consultant and every session follows it. The documents the agent produces carry your firm's branding.

Which systems can we migrate from into Sage X3?

Common sources are Sage 300, Sage 100, Dynamics GP, Sage 200, Dynamics NAV, Epicor and QAD. The agent also reads Excel, CSV and XML exports and most systems with an API or a database.

Is client data safe?

superglue holds a SOC 2 Type 2 report and works under GDPR. Credentials are encrypted with AES-256. On the Enterprise plan, superglue can run on your own infrastructure.

How do we start?

Start with one live Sage X3 project. Connect the client's systems, give the agent the statement of work, and run the first steps together with us.