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

Sage X3 implementation plan

A Sage X3 implementation plan turns the statement of work into tasks with owners, dates and dependencies. Most of the risk in a Sage X3 project is decided here: the structure, the scope of history, and who owns the data cleanup. superglue's agent drafts the plan from your kickoff documents and keeps it in a project that every later step reuses.

How this step works

What the agent does

  • Reads the statement of work, kickoff notes and uploaded exports, and extracts scope, entities and milestones.
  • Drafts tasks with owners, due dates and dependencies, grouped by workstream.
  • Turns open questions into client tasks, so blockers are visible early.
  • Keeps the project context, so later sessions know the client, the systems and the decisions already made.

What you decide and approve

  • The scope of the engagement and what is out of scope.
  • Owners, dates and the milestones the client signs.
  • Which playbook the project follows, built-in or your firm's own.

What the client gets

  • A project plan with tasks, owners, dates and dependencies.
  • A list of open questions and the client tasks that unblock them.

What to get right in a Sage X3 plan

  1. 01

    Agree the activity codes first

    Activity codes switch features, screens and field sizes on or off in a folder. Some are set when the folder is created, and every change needs a folder revalidation. Plan them before configuration starts.

  2. 02

    Create the account core model before the companies

    Each legal company links to an account core model with its ledgers, charts of accounts and dimension types. The model must exist before the company, so its design is on the critical path.

  3. 03

    Choose the release for go-live

    Sage ships X3 releases in or around May and November, and each release gets 24 months of maintenance. Agree the release the client goes live on, and when the first upgrade follows.

  4. 04

    Start the Sage 300 route early

    For Sage 300 clients, Sage offers a Data Migration Tool add-on that maps Sage 300 data to X3 import templates. Access needs two Sage eLearning courses, so put them in the plan.

  5. 05

    Set up the web services in the first week

    A SOAP web service works only after it is published in the client's folder and a connection pool is configured for it in Syracuse. Each client sets these up differently, so plan the interface setup as a task, not as something that already exists.

  6. 06

    Check the web service license before the loads

    Sage licenses SOAP web services by data volume over a period, not per user. Past the limit, calls slow down, and past the grace limit they are blocked. Size large loads against the client's license, or run them through import templates.

Frequently asked questions

What should a Sage X3 implementation plan decide first?

Agree the activity codes first; Create the account core model before the companies; Choose the release for go-live; Start the Sage 300 route early; Set up the web services in the first week; Check the web service license before the loads. These decisions shape every later step, so they belong in the plan.

Can the agent build the plan from our existing documents?

Yes. Upload the statement of work and kickoff notes, or connect the drive, Slack or Teams channel where they live. The agent drafts the plan and asks only where a business decision is missing.

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.