Sage 300 CRE

Wanita Grenier
Updated

STACK Takeoff & Estimate integrates with Sage 300 Construction and Real Estate (CRE) to streamline the flow of data between preconstruction and accounting. This integration allows you to import active Sage 300 jobs into STACK and export completed estimates back into Sage 300—reducing manual data entry, improving accuracy, and minimizing friction during project setup and estimate handoff.

The integration uses the Agave Connector to securely connect STACK with your on-premise Sage 300 CRE environment.

Key Information

  • The Sage 300 CRE integration allows you to import active Sage 300 jobs into STACK and export completed STACK estimates to Sage 300 CRE Job Cost (Direct Costs) and Sage 300 CRE Estimates.

  • To use the integration, you must be running Sage 300 CRE version 17.1 (2019) or newer, be on a supported Windows environment, have the Agave Connector installed and running, and have a properly configured STACK library with items, cost types, and accounting codes.

  • Exports are additive, meaning re-exporting an estimate adds new costs in Sage 300 rather than replacing existing ones, and closed Sage 300 jobs will not appear as options for import or export.

  • Missing or invalid accounting data—such as cost codes or cost type mappings—can prevent an export from completing successfully.

Install Agave Connector

The Agave Connector is a Windows application that enables secure communication between STACK and Sage 300 CRE.

Before you begin

  • Confirm you are running a supported version of Windows (Windows 10, 11, Windows Server 2016, 2019, 2022)

  • Install the connector on the server hosting Sage 300 CRE, not a user workstation

  • Use a dedicated or shared Windows account so access is not tied to a single individual

Installation steps

  1. Contact support@agaveapi.com to request the Agave Connector download link.

  2. Download and run the installer (.exe file).

  3. Complete the installation and setup, refer to the Agave Step-by-step instructions.

  4. Once installed, the Agave Connector application will open automatically.

Connect to Sage 300 CRE

  1. In STACK, click your Profile Icon in the upper right corner.
    SelectProfileIcon.png
  2. Select Account Settings.
    AccountSettings.png
  3. In the left side panel, choose App Integrations.
    AppIntegrations.png
  4. Scroll down or use the search bar to find Sage 300.
    Sage300Tile.png
  5. In the Sage 300 tile, click Connect.
    SageConnect.png

  6. Confirm system requirements and select Continue.
    Sage300ContinueConnect.png

  7. Choose Create Account.
    CreateAccountConnect.png

  8. Open the Agave Connector and select Add Account → Sage 300 CRE.
    AddAccountConnect.png

  9. Fill in the Database Configuration fields:

    1. Company filepath: Should fill in automatically with your company name

    2. Sage 300 CRE username: The Username you used to log into Sage 300 CRE.

    3. Password: The password you used to log into Sage 300 CRE.
      DatabaseConfiguration.png

  10. Click TEST AND SAVE.
    DatabaseConfigSave.png

  11. Copy the generated Account ID and Token  from the Agave Link Component into STACK.
    AgaveAPI.png

  12. Click TEST AND SAVE.
    AgaveAPISave.png

  13. Select Validate Connection.
    ValidateConnection.png

NOTE: The Agave Connector must remain running to allow STACK to communicate with Sage 300 CRE, but it can be minimized once connected.

Import Active Projects from Sage 300 into STACK Takeoff & Estimate

Before you start make sure:

  • The Sage 300 CRE integration is connected

  • The Agave Connector is running

  • The Sage 300 job is active

ImportProject.gif

  1. In STACK, go to the PROJECTS tab.

  2. Click the dropdown arrow next to New Project.

  3. Select New Project from Sage 300.

  4. Choose the project you want to import.

  5. Click Import project.

  6. Review the project details.

What happens next

  • STACK creates a new project using the Sage 300 job details

  • If a job doesn’t appear:

    • Confirm it is active in Sage 300

    • Confirm the connector is running

    • Confirm the correct company is selected

Export Completed Estimates from STACK Takeoff & Estimate into Sage 300

Before you start

Make sure:

  • The STACK project is linked to a Sage 300 job

  • Your estimate is complete

  • Accounting codes and cost types are assigned and mapped correctly

ExportEstimate.gif

  1. In STACK, select the PROJECTS tab.

  2. Open the project for which you want to esport an estimate.

  3. Select the ESTIMATE tab.

  4. Double click on the Estimate Worksheet you want to export.

  5. Review your estimate:
    Line items have accounting codes
    Cost types are mapped
    The estimate contains at least one line item

  6. Click the three dots in the upper right corner.

  7. Select Export.

  8. Choose Sage 300 CRE.

  9. Click Continue.

  10. Select the export destination:
    Job Cost (Direct Costs)
    Estimates (if available)
    NOTE: Closed jobs will not appear

    NOTE: Closed jobs will not appear

  11. Click Continue.

  12. Review the mapping and edit any errors if required.

    IMPORTANT: All errors must be resolved before exporting

  13. Click Export.

  14. Click Done.

  15. Review the export results summary.

After the Export

  • Costs are added to Sage 300

  • Items with zero quantity or $0 subtotal may be skipped

  • Item names longer than 30 characters may be shortened

Mapping

Estimate export mapping (high level)

Sage 300 Field What It Represents STACK Field
Cost Code ID The detail-level cost code used to track the type of work in Sage 300. Cost codes must exist in Sage 300 and match exactly. Accounting Code
Cost Type ID The cost category associated with the line item, such as Labor, Material, Equipment, or Subcontractor. Cost Type
Current Amount The current budgeted amount, calculated as quantity × unit cost, reflecting any updates or revisions. (Revised) Extended Cost
Original Amount The original budgeted amount based on the initial quantity and unit cost. Extended Cost
Description

For Direct Costs: The name of the item from STACK 

For Estimates: Shows as "Imported Estimate" since item names cannot be set for estimate budget line items

Names longer than 30 characters may be shortened.

 Item Name
Quantity The planned quantity for the line item. Purchase Quantity
Unit of Measure The unit used to measure the quantity (e.g., hours, each, linear feet). Unit of Measure
Unit Cost The cost per unit, calculated as total cost divided by quantity. Unit Cost

Best Practices and Rules

Area Rule / Requirement Behavior
Cost codes Use detail-level cost codes only (no parent/summary codes). Summary codes can’t be posted to and will fail export.
The cost code must already exist in Sage 300. If it doesn’t exist in Sage 300, the export fails.
The cost code format must match Sage 300 exactly. Mismatched formatting can cause export errors.
Every exported line item must have a cost code. Line items without cost codes can’t be exported.
Cost types* Cost types must be mapped to Sage 300 categories. Unmapped cost types cause export errors.
Multiple cost types per item are supported. Each cost type exports as its own entry in Sage 300.
Line items Keep names under 30 characters when possible. Longer names are automatically shortened.
Line items must have quantity and cost to export. Zero-quantity or zero-cost line items are skipped.
Other costs Distributed other costs are included in line items. They are not exported separately.
Non-distributed other costs are not supported by Sage 300  Estimates require a category
Other costs with a $0 total are not exported. $0 total other costs are skipped.
Export Behavior Fix validation errors before exporting. Validation errors block the export until resolved.
Review export results after completion. Export failures are reported after the export runs.
Re-exporting adds costs in Sage 300. Exports are additive—review to avoid duplicates.

*Note about cost types: STACK exports the purchase quantity and subtotal per cost type. The subtotal per cost type includes distributed costs and is not equal to the extended cost shown in the STACK UI.

Common Issues and How to Fix Them

Issue What to Do
Missing or invalid accounting codes Open the Estimate Worksheet and confirm every exported line item has a valid accounting code that exists in Sage 300 and matches the exact format.
Cost types not mapped Go to your STACK cost type mappings and ensure every cost type used in the estimate is mapped to a corresponding Sage 300 category.
Summary-level cost codes used Replace parent or summary cost codes with detail-level cost codes, since Sage 300 does not allow posting costs to summary codes.
Agave Connector not running Verify the Agave Connector application is open and running on the Sage 300 server; reopen it if it was closed or restarted.
Unsupported Sage 300 or Windows version Confirm you are running Sage 300 CRE version 17.1 (2019) or newer and that the server is on a supported Windows version before retrying the export.
Warnings during export Review all warnings carefully before exporting, as they indicate items that may be skipped, shortened, or modified during export.
Export completes but data is missing Open Sage 300 and verify the job cost or estimate entries were created, and review the export summary in STACK for skipped items or failures.

Quick Fix Checklist

Before importing projects or exporting estimates, confirm the following:

  • ✅ All line items include valid, detail-level accounting codes that exist in Sage 300 and match the exact format.

  • ✅ Every cost type is mapped to a Sage 300 category.

  • ✅ No summary or parent cost codes are used.

  • ✅ The Agave Connector is installed, open, and running on the Sage 300 server.

  • ✅ You are using Sage 300 CRE version 17.1 (2019) or newer on a supported Windows environment.

  • ✅ The estimate contains at least one line item with quantity and cost.

  • ✅ All export warnings have been reviewed and any errors have been resolved.

  • ✅ After exporting, you verified the results in Sage 300 to confirm costs were created as expected.

Next Steps

After setting up the Sage 300 CRE integration, you’re ready to start using it in your daily workflows. Begin by importing active Sage 300 jobs into STACK, then complete your takeoffs and estimates as usual. Before exporting, review your accounting codes, cost types, and warnings to ensure your estimate is ready. After exporting, always verify the results in Sage 300 to confirm job costs or estimate entries were created as expected.

Related Articles

Estimate Worksheet Overview

Export Estimate Worksheet Data

See how others use this feature in the STACK Community.

If you need additional assistance, please Contact Us.

Was this article helpful?
0 out of 0 found this helpful

Comments

Please sign in to leave a comment.