JobBoss + Go Fig
Connect JobBoss shop ERP to Go Fig for job-level costing, margin diagnostics, and manufacturing financial intelligence.
JobBoss (and JobBoss2) is the shop-floor ERP of record for thousands of small and mid-market job shops, make-to-order manufacturers, and precision machining operations. It tracks jobs, routers, work centers, material issues, and labor clockings at a granularity that QuickBooks and generic accounting can never match. The gap is analytics: JobBoss' built-in reports are list-style and tied to its SQL Server schema, so estimated-versus-actual margin by job, customer, or material class requires either Crystal Reports work or a manual export. Go Fig connects to the JobBoss SQL Server database (on-premise or hosted) via a read-only replica, lands every job, router step, labor ticket, material issue, and posted invoice in the Financial Intelligence Graph, and joins that shop-floor grain to the accounting ledger. Celeste can then diagnose estimate-versus-actual variance by job, quote accuracy by customer, work-center profitability, and on-time delivery impact on margin without a data engineer hand-writing SQL against the JobBoss schema.
Key facts
- Editions
- JobBoss classic and JobBoss2 (cloud)
- Grain
- Job, router step, labor ticket, material issue
- Backfill
- Full SQL history (5+ years typical)
- Estimate vs actual
- Quote-to-cost join preserved
- Sync cadence
- 15-minute CDC or hourly snapshot
What you can do with JobBoss data in Go Fig
Estimate-versus-actual job margin
Join quoted cost at the router-step level to actual labor, material, and outside-process spend so finance and operations see exactly where margin leaks appeared, which customer or material class they concentrate in, and whether estimator bias is systematic.
Work-center and labor profitability
Analyze labor-ticket throughput, setup-versus-run ratios, and work-center utilization alongside the revenue attributable to jobs that passed through each cell. Shop floor decisions (capacity, crewing, second shift) get financial evidence attached.
Customer and part-family segmentation
Segment jobs by customer, part family, and job type to see which customers actually make money after realized scrap, rework, and overtime, and which are cross-subsidized by the good ones. A margin-compression diagnosis that JobBoss reports alone cannot assemble.
Data available from JobBoss
Go Fig extracts and normalizes the following data from your JobBoss account:
How to connect JobBoss
Provision read-only database access
For on-premise JobBoss, create a SQL login with db_datareader on the JobBoss database (typically named JobBOSS or JB_Data). For JobBoss2 cloud, generate a scoped API key. If the database lives behind a firewall, install the Go Fig read-only agent on a Windows host that can reach the SQL Server, or set up an IP-allowlisted VPN tunnel.
Select companies, plants, and historical window
Shops running multiple plants or legal entities pick which to sync per connection. Historical backfill is typically 5+ years because job-shop margin trends only show up over a long tail of jobs; JobBoss retains this history indefinitely in the SQL schema, so backfill depth is a storage decision rather than a source limit.
Map router operations and cost categories
JobBoss stores estimated and actual values on separate tables at different grains. Go Fig reconciles them by job and operation, and Celeste pre-suggests a mapping of JobBoss cost categories (direct labor, burden, material, outside process, freight) into your management P&L structure so estimate-versus-actual rollups match how finance reports gross margin.
Join to the accounting ledger
JobBoss posts summarized journal entries into QuickBooks, Sage, or another GL depending on how your shop is wired. Go Fig keeps both the shop-floor grain and the posted GL so you can trace a margin variance from the consolidated P&L down through the posted summary to the individual router-step labor ticket where it originated.
Authentication: Read-only SQL Server credentials against the JobBoss database (or a read replica). For JobBoss2 (cloud), Go Fig connects via the hosted API with a scoped API key. For on-premise deployments, a dedicated Windows or SQL login with db_datareader on the JobBoss database is provisioned, typically connected through an agent or VPN tunnel so the database does not need to be exposed publicly.
Common Questions About JobBoss Integration
Does Go Fig work with both legacy JobBoss and JobBoss2?
Yes. Legacy JobBoss (SQL Server-backed, on-premise or hosted) is connected through a read-only SQL login; JobBoss2 (ECI's cloud product) is connected through its API with an API key. The downstream data model is reconciled so dashboards and flows built on one deployment carry over if you migrate between them. Shops mid-migration can sync both in parallel to keep reporting continuous through the cutover.
How are estimated versus actual job costs joined?
JobBoss stores estimated cost on the quote and operation-standard tables and actual cost on labor-ticket, material-issue, and PO tables. Go Fig builds a reconciliation at job and router-step grain, preserving both sides, so estimate-versus-actual variance is queryable by job, customer, part family, work center, and material class. Most shops find their first real margin insight within the first week of running this join.
Can Go Fig handle outside-process (OSP) PO costs and landed cost?
Yes. Outside-process POs are joined to the router step they relate to, so OSP spend lands in the actual-cost side of the margin equation rather than getting lost in overhead. Landed-cost uplift (freight-in, duty, handling) is preserved when JobBoss tracks it; if your team posts landed cost manually in accounting, Go Fig can apply an allocation flow on top so management margin reflects the true cost of bringing parts back to the shop.
How does Go Fig deal with scrap, rework, and non-conforming material?
Scrap and rework transactions are first-class in the JobBoss schema and are preserved as distinct cost events in Go Fig, tagged by reason code. That makes cost-of-poor-quality visible at the job, customer, and work-center level, which is often the single largest hidden driver of margin compression in job shops. Celeste can report on COPQ by customer or part family directly without you hand-writing SQL against MfgIssue and related tables.
What's the sync strategy for an on-premise SQL deployment?
Go Fig prefers change-data-capture (CDC) on the JobBoss database where SQL Server CDC is enabled. If CDC is not available, hourly snapshot sync with change-detection on updated_time columns is the default. Backfills run during off-shift hours to avoid contention with shop-floor data entry. Customers with a hosted JobBoss instance commonly run the Go Fig agent on the same Windows host that hosts the database so there is no network hop cost.
Ready to connect JobBoss?
See how your JobBoss data looks in Go Fig with a personalized demo.
Book a Demo