Step 3 of 11 · Pre-implementation · Updated November 19, 2026

Sage X3 data assessment

A data assessment tells you what data exists, how much of it there is, and whether it is ready to move to Sage X3. Problems found here cost hours. The same problems found at cutover cost the go-live date. superglue's agent reads the source system read-only, counts and tests the records that matter, and reports readiness in plain language.

How this step works

What the agent does

  • Reads the source system and makes focused read-only queries. Nothing is written.
  • Builds an inventory of entities, record counts, date ranges and relationships.
  • Tests data quality with real counts: duplicates, missing values, orphaned references and inconsistent codes.
  • Reports readiness as ready, ready with caveats, or blocked.

What you decide and approve

  • Which modules and how much history are in scope.
  • Which issues the client fixes in the source and which the mapping handles.
  • When the findings are good enough to start mapping.

What the client gets

  • A data readiness report with counts and examples.
  • A cleanup list for the client team.

What to look for before a Sage X3 migration

  1. 01

    Find partners that are customers and vendors

    Sage X3 keeps each trading partner once as a business partner with several roles. Count the legacy customers and vendors that are the same company before mapping starts.

  2. 02

    Test samples against the import templates

    An object import runs the same checks as interactive entry. A record that a user could not save in Sage X3 also fails the import, so test real samples early.

  3. 03

    Check that each item has a clear group

    Product categories give new products and product-site records their defaults, such as units, the accounting code and the valuation method. Legacy items need a group that maps to one category.

  4. 04

    Measure the largest journal

    Activity codes size the number of lines on journal entry screens. Find the largest legacy journal, so the folder is sized for the opening balance and history loads.

Frequently asked questions

What should you check before a Sage X3 migration?

Find partners that are customers and vendors; Test samples against the import templates; Check that each item has a clear group; Measure the largest journal. The agent checks these read-only and reports readiness.

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.