Migrating a finance team off hand-built spreadsheet packs is mostly a logistics problem, not a technology problem. Here's exactly what the OPEX FP&A onboarding does, so you can prepare the three things it asks for.
Before you start
- An OData BaqSvc base URL. It looks like
https://yourserver/yourinstance/api/v2/odata/YOURCOMPANY/BaqSvc. Your Epicor admin can confirm it — it's the same root the REST interface uses. - Credentials. An API key, or a service account username/password. A read-only account is enough: the wizard only reads BAQs, it never writes to Epicor.
- The deployed BAQs. The portal expects the OFPA-BAQ pack
(
OFPA-Company,OFPA-Book,OFPA-ASV,OFPA-GLAccounts,OFPA-COACategory,OFPA-TB). If you don't have them yet, contact us and we'll share the definitions.
What the wizard does
Step 1 — connection. Paste the base URL, pick the auth method, and hit
Test connection. The wizard builds exactly the headers the runtime will use
later and probes OFPA-Company. Nothing is saved until that probe succeeds —
no half-configured states.
Step 2 — initial sync. One click runs six syncs in order: companies, books, account segments, GL accounts, report categories, and the fiscal calendar. Then it picks the newest fiscal year and period from the calendar you just synced and pulls that trial balance. Each step shows its row count, so you can see the shape of your data immediately.
Step 3 — report. You land on the overview with real data. Every report keeps its own Sync ERP button for refreshes, and the journal drill-down works from there.
Demo mode, no pressure
Not ready to point it at production Epicor? The wizard has a Continue with demo data escape hatch that seeds realistic sample data instead — same reports, same Excel add-in, zero risk.
That's the whole migration. The spreadsheets don't disappear on day one, but from day one they have something to be checked against.