
How to migrate from SAP ECC to Sage X3
To migrate a client from SAP ECC to Sage X3 with superglue's AI agent, connect the client's SAP ECC system, and give superglue access to the client's Sage X3 account. superglue assesses the data in minutes, plans every phase, recommends an answer to each decision, and runs trial loads that reconcile to the cent before cutover. You review, decide and sign off with the client.
SAP ends mainstream maintenance for SAP ERP 6.0 with enhancement packages 6 to 8 at the end of 2027, and paid extended maintenance runs to the end of 2030, so most ECC clients plan their move now.
What are the steps to migrate from SAP ECC to Sage X3?
Migrating from SAP ECC to Sage X3 takes six steps: connect both systems, assess the data, plan every phase, decide the mapping, run trial loads and cut over. Each load repeats exactly what you tested, and every write waits for your approval.
- 01
Connect SAP ECC and Sage X3
Connect SAP ECC read-only through the services the client's SAP team exposes, such as OData on SAP Gateway, or upload the extracts the team runs. superglue writes nothing. The client then gives superglue access to Sage X3.
- 02
Assess the SAP ECC data
In minutes, superglue counts every record, finds the open items and lists the data issues with examples. You know the size of the migration before you quote it.
- 03
Plan every phase
superglue drafts the plan from discovery to cutover, with tasks, owners and the SAP ECC specifics already in it.
- 04
Decide the mapping
superglue brings each decision below with a recommendation from the client's own data. You confirm or change each answer, and the client signs the mapping.
- 05
Run the trial loads
superglue loads a Sage X3 test folder and compares it with SAP ECC: the trial balance per period, the open receivables and payables per customer and vendor, the uncleared bank items, and the inventory value. superglue explains every difference, and you repeat the trial load until a full run reconciles with no new differences. The last run is a timed rehearsal of the cutover.
- 06
Cut over
At cutover, the client stops entry in SAP ECC, and superglue loads the open items with the same steps as the trial loads. After the client closes the last period in SAP ECC, superglue loads the final balances, and you sign the reconciliation with the client.
How do you get the data out of SAP ECC?
- ECC has no general-purpose OData API for finance and master data. OData exists only for specific Fiori apps or for services built on SAP Gateway. The client's SAP team exposes the tables superglue needs to a technical user, or runs the extracts, and the superglue gateway reaches the system on the client's network.
- Ask which company codes, plants and sales organizations are in scope, because one ECC system often runs several countries.
- Ask which years were archived. Archived documents are no longer in the database, so those years move as balances.
On-premise clients install the superglue gateway once: Connecting to on-prem systems
What needs to be configured in Sage X3?
The client adds a Sage X3 user for superglue and names the folder superglue loads into. superglue configures Sage X3 and loads the data through that access, in a Sage X3 test folder first, in this order:
- 01
The charts of accounts and the analytical dimension types.
- 02
The ledgers and the account core model.
- 03
Companies and sites, with the legislation and the currencies of each company.
- 04
The fiscal years and periods of each company, and the dimension values.
- 05
Accounting codes, payment terms and tax codes.
- 06
Customers, suppliers and products, then the opening balances and the open items through import templates.
What moves from SAP ECC to Sage X3?
| In SAP ECC | In Sage X3 |
|---|---|
| G/L accounts per chart of accounts and company code | General accounts |
| Cost centers, profit centers and business areas | Analytical dimensions |
| Customers | Customers |
| WBS elements in Project System | Projects |
| Vendors | Suppliers |
| Materials | Products |
| House banks and bank accounts | Bank accounts |
Open items
Open receivables and payables items, open sales and purchase orders, and stock per plant and storage location with its valuation.
Open items load as customer and supplier open items with their original numbers, dates and due dates, so the aging in Sage X3 matches on day one.
History
ECC keeps G/L balances per period and every document that was not archived. superglue reads the balances for the years the client wants to keep and reports which years were archived.
History loads as journal entries per period, account and dimension.
Which decisions do you make when you migrate from SAP ECC to Sage X3?
- 01
Where do company codes, plants and profit centers go?
SAP ECC keeps the legal books per company code and logistics per plant, and reports through cost centers and profit centers. In Sage X3, each site belongs to one company, and a site that is not a financial site posts through a financial site of its company.
superglue maps each company code in scope to a Sage X3 company, each plant to a site of that company, and the cost centers and profit centers in use to dimension types. Decide early which plants become financial sites, because the flag is hard to change once the site has postings.
- 02
How does the stock valuation move?
SAP ECC values each material at a standard price or a moving average price, set by its price control, per plant or per company code depending on the valuation level of the system. Sage X3 sets the valuation method per product and site.
superglue proposes standard cost for materials with a standard price and cumulative average cost for materials with a moving average price. It loads the ECC standard price as the Sage X3 standard cost before the opening stock, so the stock value matches ECC.
- 03
How many companies and sites does the client need?
In Sage X3, a company keeps the legal books, and sites hold the financial, sales, purchasing, inventory and production activity.
superglue recommends one company for each legal company in SAP ECC, and a site for each location that keeps inventory or its own books.
- 04
Which analytical dimensions does the client need?
Sage X3 records analytical dimensions on journal lines, each account can require or default them, and the client chooses which dimension types to use.
superglue proposes dimension types from the segments and fields the client actually reports on.
- 05
Which cutover date does the client use?
A cutover on the first day of a period lets the open items and balances load as of one date. A fiscal year start keeps the year's reports and year-end filings in one system, and a date in the middle of the year means combining two systems for the audit and the tax returns. Avoid a date when the team must close the books or report results.
superglue recommends the first day of a month, and the first day of the fiscal year when the client can wait for it. The final balances load after the last period in SAP ECC is closed.
- 06
How much history moves?
Most clients need the open items plus one to three years of monthly balances in Sage X3, at least the current and the prior fiscal year for comparison, and older years as yearly balances. The client keeps the older detail in an archive.
superglue recommends two years of monthly balances per account, and full transaction detail only where the client needs to look into single transactions.
What are the common challenges when you migrate from SAP ECC to Sage X3?
The client's SAP team sets the pace
ECC has no standard API for finance and master data, so every extract and every technical user goes through the client's SAP team. Their queue often decides when the assessment can start, so request access in the first week.
Years of unused records
ECC systems that run for 15 years or more hold many customers, vendors and materials nobody uses. Agree a cut-off with the client, such as no activity in two years. superglue lists the records without activity, so only live data moves.
Custom fields and tables hold business data
Most ECC systems have Z fields and Z tables that hold data the business relies on. superglue lists every custom field that holds data, so the client decides which ones come back in the new system.
Classic G/L lines have no profit center
Systems on the classic general ledger or without document splitting post many lines without a profit center or segment. superglue derives them from the cost center and the account, and lists the lines it cannot derive.
Custom code does not move
ECC customizations are written in ABAP, and Sage X3 customizations in its own 4GL. List each custom program by the business need it serves, and decide which needs Sage X3 covers as standard before anyone rewrites code.
Valuation classes decide the stock accounts
In ECC, the valuation class on each material and the account determination decide which G/L accounts stock and cost of goods sold post to. superglue reads the account determination and proposes the same posting setup in the new system, so stock postings stay the same.
Every object loads through its own import template
Sage X3 imports each object through an import template, with the same checks as manual entry, and the import log lists every record that fails. superglue builds the import files and explains every rejected record.
Customers and suppliers are business partners
Sage X3 keeps each trading partner once as a business partner, which can be a customer, a supplier or both. Agree with the client how duplicates across the old customer and vendor lists merge.
Activity codes switch features on
Sage X3 turns features and field sizes on with activity codes. Some are set when the folder is created, and every change needs a folder revalidation. Agree the activity codes in the design phase.
Open items must not count twice
Open invoices and bills post to the receivables and payables accounts when they load, and the opening trial balance holds the same amounts. Load the open items and the opening balances against one conversion account, and check that it ends at zero.
Plan fixed assets as their own stream
The trial balance brings the cost and the accumulated depreciation, but the asset register needs each asset with its in-service date, useful life and depreciation to date, and tax books need their own values. Agree early where the register lives after go-live, and reconcile it to the asset accounts.
superglue also runs the rest of the Sage X3 project. See the Sage X3 implementation
Frequently asked questions
Which data moves from SAP ECC to Sage X3?
The chart of accounts, customers, vendors and items, the open items, and as much history as the client needs. The mapping table on this page shows where each record lands in Sage X3.
Does superglue write to Sage X3 without my approval?
No. superglue only reads SAP ECC. Before any write to Sage X3, it shows the target, the connection and a transformed sample, and waits for your approval.
How do I know the migration is complete?
superglue reconciles the trial load and the final load against SAP ECC: the trial balance per period, the open receivables and payables per customer and vendor, the uncleared bank items, and the inventory value. You get a reconciliation report to sign with the client.
What happens when I start this migration?
You sign up and connect the client's systems. If you want to see a full migration run first, superglue can set up Northwind Outdoor Supply, a sample client.
Start your SAP ECC to Sage X3 migration
Sign up and connect the client's systems, or let superglue set up Northwind Outdoor Supply, a sample client, to see a full migration run first.