Skip to main content

Go-Live

Once prerequisites are complete and the dry run succeeds, transition to production syncing with the steps below.

Run the Agave autolink process to connect ServiceTitan and ERP records for customers, vendors, and jobs that exist in both systems. Record linking relies on multiple matching criteria, with Legacy ID (from Step 0) producing the highest accuracy.

Expect some unmatched records after the autolink step. Common causes include:

  • Duplicate records in ServiceTitan or the ERP where the correct match is unclear.
  • Minor naming differences (for example, misspellings, first/last name order).

Work through stragglers manually to avoid duplicate creation once syncing starts.

Step 2: Configure go-live sync triggers​

Your Agave account manager sets production sync filters based on the agreed go-live date. Confirm the defaults meet customer expectations.

Data modelDefault sync trigger filters
VendorsStatus must be Active; sync on creation
CustomersStatus must be Active; sync on creation
JobsStart date on or after the go-live date; sync on creation
AR invoicesStatus Posted; not Exported; issue date on or after go-live
AR paymentsStatus Posted; not Exported; payment date on or after go-live
AP invoicesStatus Posted; not Exported; issue date on or after go-live
TimecardsStatus Locked or Approved

Document any deviations (for example, historical sync windows) in the onboarding tracker.

Step 3: Turn on automatic sync​

Follow the instructions at https://sync-docs.agaveapi.com/docs/service-titan-basics/automatic-syncing#enabling-automation to enable automation. Perform this during a scheduled session so the team can monitor the first production sync.

Go-live FAQ and best practices​

Document integrations — migrating to a new ERP​

Option 1: Import open activity and balances into the new ERP

  • If the ERP offers a migration mode that suppresses GL posting, import open AR invoices and payables without generating journal entries.
  • Create a balancing journal entry so detailed listings tie to the trial balance.

Option 2: Close open activity in the legacy ERP

  • Continue processing open AR/AP transactions in the previous ERP until they are fully closed.

Journal entry integrations — migrating to a new ERP​

Import the trial balance into the new ERP using one or multiple journal entries on go-live day. ServiceTitan becomes the subledger of record for AR, so only balances need to be migrated.

Blackout period double entry​

ServiceTitan performs a final data import roughly 1–2 days before go-live. During that blackout window, users should double-enter data into both systems. Agave begins syncing transactions immediately after the final data sign-off.

What Agave does not sync​

  • Open AR invoices dated before the go-live date.
  • AR payments applied to AR invoices dated before the go-live date.

Sequence of events​

Journal entry integrations

  1. Set the go-live date.
  2. Import trial balances on the go-live day.
  3. Complete the ServiceTitan month-end close.
  4. Sync a single journal entry as a production test, then enable automatic sync.
  5. Agave syncs journal entries based on the configured triggers.

Document integrations

  1. Communicate the ServiceTitan or integration go-live date to your Agave account manager.
  2. On the final data import or go-live date, Agave:
    • Auto-links vendor, customer, and job records.
    • Applies go-live sync trigger filters.
  3. (If applicable) Complete ERP cutover tasks listed in Go-live FAQ and best practices.
  4. On go-live day, enable automatic sync.

Impact on accounting workflows​

When ServiceTitan is integrated with Agave:

  • ServiceTitan functions as the Accounts Receivable subledger for journal entry integrations.
  • ServiceTitan reporting provides total sales tax liability and jurisdiction-level breakouts for compliance.
  • Inventory counts and SKU management live in ServiceTitan, while inventory value appears on ERP financial statements.