How to migrate from Sage 50 to Sage 300
To migrate a client from Sage 50 to Sage 300 with superglue's AI agent, connect the client's Sage 50 company or upload its exports, and give superglue access to the client's Sage 300 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.
This guide covers Sage 50 US, formerly Peachtree.
What are the steps to migrate from Sage 50 to Sage 300?
Migrating from Sage 50 to Sage 300 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 Sage 50 and Sage 300
Connect the client's Sage 50 company read-only through the Sage 50 ODBC driver, or upload the standard exports. superglue writes nothing. The client then gives superglue access to Sage 300.
- 02
Assess the Sage 50 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 Sage 50 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 300 test company and compares it with Sage 50: 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 Sage 50, and superglue loads the open items with the same steps as the trial loads. After the client closes the last period in Sage 50, superglue loads the final balances, and you sign the reconciliation with the client.
How do you get the data out of Sage 50?
- The client sets a data access password in Sage 50, and the superglue gateway reads the company on a computer with Sage 50 installed. The standard exports work too.
- Ask whether old years were purged. Purged transactions are gone, so those years move as balances.
- Sage 50 keeps each company in its own folder, so ask for every company in scope.
The client installs the superglue gateway once: Connecting to on-prem systems
What needs to be configured in Sage 300?
The client adds a Sage 300 user for superglue with access to the Sage 300 Web API, and the superglue gateway reaches it on the client's network. superglue configures Sage 300 and loads the data through that access, in a Sage 300 test company first, in this order:
- 01
The company profile, the fiscal calendar and the functional currency. Multicurrency cannot be turned off once it is on.
- 02
The account structure with its segments, then the GL accounts.
- 03
Account sets for receivables, payables and inventory, so every subledger posts to its control account.
- 04
Bank codes, terms, tax authorities and tax classes.
- 05
Customers, vendors and items, then the opening balances and the open items.
What moves from Sage 50 to Sage 300?
| In Sage 50 | In Sage 300 |
|---|---|
| Chart of accounts | GL accounts |
| Departments in the account IDs | Account segments |
| Customers | Customers |
| Jobs, with phases and cost codes in Premium and higher | Contracts and projects in Project and Job Costing, loaded by import because the Web API has no endpoints for them |
| Vendors | Vendors |
| Inventory items | Items |
| Cash accounts | Bank codes |
Open items
Open invoices and credit memos, open purchases and vendor credits, open sales and purchase orders, and inventory on hand with its cost.
Open items load as AR and AP invoices with their original numbers, dates and due dates, so the aging in Sage 300 matches on day one.
History
Sage 50 keeps every transaction that was not purged. superglue reads all of them and reports how far back the detail goes.
History loads as GL journal entries per period and account.
Which decisions do you make when you migrate from Sage 50 to Sage 300?
- 01
Where do Sage 50 departments go?
Sage 50 usually tracks departments as a suffix in the account ID, such as 6100-01. Sage 300 keeps them as an account segment.
superglue maps the department part of each account ID to a Sage 300 segment.
- 02
Where do Sage 50 jobs go?
Sage 300 tracks jobs in Project and Job Costing, with contracts, projects and categories.
superglue recommends a contract and a project for each open job, and history only for closed jobs.
- 03
Does the client add a new company or join an existing one?
Each Sage 300 company keeps its own books. A new legal entity usually becomes a new company, and consolidations bring the companies together.
superglue recommends a new Sage 300 company for each legal company in Sage 50, with the account structure of the client's existing companies.
- 04
Which account sets does the client need?
Account sets decide the control accounts for receivables, payables and inventory.
superglue proposes account sets from the control accounts the client used, so each subledger agrees with the general ledger.
- 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 Sage 50 is closed.
- 06
How much history moves?
Most clients need the open items plus one to three years of monthly balances in Sage 300, 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 Sage 50 to Sage 300?
Purged transactions leave gaps in the history
Sage 50 lets users purge old transactions, and the detail of those years is gone. superglue reports the first year with full detail, and moves the earlier years as balances.
Departments become an account segment
Many Sage 50 companies repeat each account per department, such as 6100-01 and 6100-02. In Sage 300, the department becomes its own account segment, and each account and department pair stays a GL account. superglue maps the suffix to the segment and checks every pair against the account structures.
Reported years still change
Sage 50 keeps two fiscal years open, and clients post into the earlier year after its figures were reported. superglue compares each reported year with the approved trial balance before the history moves.
Multi-company clients need an intercompany plan
Clients with several companies keep one company folder for each, with intercompany balances between them. Agree early which companies merge, which become entities, and how the intercompany balances settle. superglue reads every company and matches the intercompany balances.
Each company is its own database
A new legal entity in Sage 300 is a new company with its own database. Set up Intercompany Transactions before the first load if the companies trade with each other.
Every account needs an account structure
Each GL account has an account structure that lists the segments it uses. Agree the structures before the chart of accounts loads.
Optional fields come before the data
Optional fields on customers, vendors and transactions must exist before the records that use them load. superglue creates them from the signed mapping first.
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.
Frequently asked questions
Which data moves from Sage 50 to Sage 300?
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 300.
Does superglue write to Sage 300 without my approval?
No. superglue only reads Sage 50. Before any write to Sage 300, 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 Sage 50: 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 Sage 50 to Sage 300 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.