How to migrate from Sage 300 CRE to Sage Intacct
To migrate a client from Sage 300 CRE to Sage Intacct with superglue's AI agent, connect the client's Sage 300 CRE server, and give superglue access to the client's Sage Intacct account. superglue assesses the data in minutes, plans every phase, recommends an answer to each decision, and runs a trial load that reconciles to the cent before cutover. You review, decide and sign off with the client.
What are the steps to migrate from Sage 300 CRE to Sage Intacct?
Migrating from Sage 300 CRE to Sage Intacct takes six steps: connect both systems, assess the data, plan every phase, decide the mapping, run a trial load and cut over. Each load repeats exactly what you tested, and every write waits for your approval.
- 01
Connect Sage 300 CRE and Sage Intacct
Connect Sage 300 CRE read-only through the Timberline ODBC driver on the client's server. superglue writes nothing. The client then gives superglue access to Sage Intacct.
- 02
Assess the Sage 300 CRE 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 300 CRE 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 load
superglue loads a Sage Intacct sandbox or implementation company and compares it with Sage 300 CRE: the trial balance per period, the open receivables and payables with their retainage, and the cost to date and open commitments per job, cost code and category. superglue explains every difference before cutover.
- 06
Cut over
At cutover, superglue loads the final data with the same steps as the trial load, and you sign the reconciliation with the client.
How do you get the data out of Sage 300 CRE?
- The superglue gateway runs on the Sage 300 CRE server, because the Sage ODBC driver comes only with a Sage installation. The client's Sage admin creates a read-only user with ODBC access and no Payroll.
- One server often holds live companies, copies and archives. superglue opens every company and shows which ones are active, so the client confirms the scope.
- superglue leaves payroll, tax IDs and bank details out of every read.
The client installs the superglue gateway once: Connecting to on-prem systems
What needs to be configured in Sage Intacct?
The client authorizes the superglue sender ID in Sage Intacct and adds a user for superglue. superglue configures Sage Intacct and loads the data through that access, in a Sage Intacct sandbox or implementation company first, in this order:
- 01
Multi-entity, the base currencies and the first fiscal month. Base currencies and the first fiscal month can change only before transactions exist.
- 02
The configuration of each module, such as General Ledger, Accounts Payable and Accounts Receivable, and the names of terms and dimensions.
- 03
Entities, locations, departments and the other dimensions.
- 04
The chart of accounts and the journals.
- 05
Customers, vendors and items, then the opening balances and the open items.
Access setup for the client: Sage Intacct configuration guide
What moves from Sage 300 CRE to Sage Intacct?
| In Sage 300 CRE | In Sage Intacct |
|---|---|
| General ledger accounts | GL accounts |
| Account prefixes and suffixes | Dimensions such as departments, locations and classes |
| Customers | Customers |
| Jobs, extras, cost codes and categories | Projects |
| Vendors and their compliance records | Vendors |
| Bank accounts | Checking and credit card accounts |
Open items
Open AP invoices with the retainage held, open billings with the retainage receivable, open subcontracts and purchase orders with their remaining amounts, and the cost to date per job.
Open items load as AR invoices and AP bills with their original numbers, dates and due dates, so the aging in Sage Intacct matches on day one.
History
superglue reads the job cost history per job, cost code and category, and the general ledger history per period.
History loads as summary journal entries per month, account and dimension.
Which decisions do you make when you migrate from Sage 300 CRE to Sage Intacct?
- 01
How do job, extra, cost code and category fit Sage Intacct?
Sage 300 CRE nests job, extra, cost code and category. Sage Intacct tracks this structure as project, task and cost type only with its Construction subscription, so confirm the client licenses it before you quote.
superglue maps each job to a project, each cost code to a task, with its extra where the client uses extras, and each category to a cost type. superglue shows this mapping with examples from the client's own jobs, because it is the hardest mapping of the project.
- 02
How does retainage move?
Sage Intacct Construction tracks retainage on AR invoices and AP bills, and releases it with its own transactions.
superglue moves open retainage per job and per invoice, so the retainage aging matches Sage 300 CRE.
- 03
Where do the account prefixes go?
In many Sage 300 CRE companies, the first prefix of the account number stands for a legal entity. Other prefixes often stand for divisions or departments.
superglue recommends an entity for each prefix that is a legal entity, and departments or locations for the others.
- 04
Which companies become entities, and which become locations?
In Sage Intacct, an entity has its own books, tax and bank accounts. A location only adds a reporting value.
superglue recommends one entity for each legal company in Sage 300 CRE, and locations for the sites inside a company.
- 05
Which records are shared across entities?
Customers, vendors and items can live at the top level and be shared, or belong to one entity.
superglue recommends shared customers and vendors, so each company appears once and intercompany reporting stays clean.
- 06
How much history moves?
Most clients need the open items plus one to two years of monthly balances in Sage Intacct, 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 300 CRE to Sage Intacct?
Retainage moves as its own open item
Retainage held on subcontractor invoices and retainage receivable on billings must stay open after the move, apart from the invoice balance. superglue moves each retainage balance with its job and its commitment.
Cost codes and categories form one structure
Sage 300 CRE tracks cost by cost code and category, such as concrete with labor, material and subcontract. superglue maps that pair as one structure, so job cost reports keep their meaning.
Account prefixes hold the company
The prefix of a Sage 300 CRE account often stands for a company or a division. superglue splits it out of the account number and proposes where it goes.
Contracts and commitments point to missing jobs
Contracts and commitments can reference jobs that are no longer in the job master. superglue checks every job reference against the job master and the archive companies.
One server holds live companies and old copies
A Sage 300 CRE server often keeps live companies, copies, sandboxes and job archives side by side. superglue opens every company folder and reports which ones are active before the scope is set.
Job costing may have moved elsewhere
Some companies still post GL and AP in Sage 300 CRE while project managers run jobs in another system, and the job cost module sits idle for years. superglue profiles the activity of each module before the scope is set.
Project managers reconcile in job cost
Project managers trust the job cost reports more than the general ledger. superglue reconciles cost to date and open commitments per job, cost code and category, in addition to the trial balance.
Plan module configuration as its own workstream
In Sage Intacct, the settings of General Ledger, Accounts Payable and the other modules cannot be imported like data. Unless the partner starts from a template company, they are set by hand, screen by screen. superglue sets them and checks every value, so the configuration is ready when the data is.
Agree user-defined dimensions with the person who reports on them
A user-defined dimension stays in Sage Intacct once it holds data. Add only the ones the client will report on, and get each one agreed before the first load.
superglue also runs the rest of the Sage Intacct project. See the Sage Intacct implementation
Frequently asked questions
Which data moves from Sage 300 CRE to Sage Intacct?
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 Intacct.
Does superglue write to Sage Intacct without my approval?
No. superglue only reads Sage 300 CRE. Before any write to Sage Intacct, 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 300 CRE: the trial balance per period, the open receivables and payables with their retainage, and the cost to date and open commitments per job, cost code and category. 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 Pinecrest Supply, a sample client.
Start your Sage 300 CRE to Sage Intacct migration
Sign up and connect the client's systems, or let superglue set up Pinecrest Supply, a sample client, to see a full migration run first.