Campfire implementation
A Campfire implementation that survives its first real close
Configuration is the easy half. The half that decides whether month-end works is the policy decided before the build, the history migrated at the right granularity, and the systems around the ledger tested before the close depends on them.
Scope
What an implementation has to settle
Every one of these is a decision, and every one of them is cheaper to make before configuration than after.
01
Entities and consolidation
Legal entities, intercompany, currencies and the consolidation your reporting depends on, configured before any history is loaded.
02
Chart of accounts
The accounts you actually report on, mapped from the old system, with the ones nobody has used since 2019 left behind deliberately.
03
Revenue policy
How recognition works for your billing models, agreed with whoever signs the financials, and configured so the schedule is reproducible.
04
Opening balances and history
How much history comes across and at what granularity, reconciled to the prior system before you rely on a single report.
05
The systems around the ledger
Banking, AP, payroll, billing, tax and FP&A connectors, plus anything that needs API work because no connector exists.
06
Close process
Checklists, reconciliations and flux review set up as a process your team runs, not as a demo someone gave once.
Options
Three ways to run it
Campfire’s own team
Fits when
A finance-only rollout: one or few entities, standard billing, few systems touching the ledger.
Watch for
Implementation is the vendor’s, so scope questions that reach into other systems tend to land back on your team.
Seibert Consulting Group
Fits when
The work reaches past the ledger: a NetSuite migration, a storefront, inventory, or an integration nobody has built.
Watch for
We are the accountable party for the outcome across those systems, not only for the ledger configuration.
Both, deliberately split
Fits when
Campfire configures the core while we handle migration and the integration layer, on one plan with one timeline.
Watch for
The split only works when the boundary is written down before the work starts. We will write it down.
Campfire implements its own product and does it quickly for a standard finance rollout. We will say so when that is the right route for you. Talk it through →
Process
How the project runs
1
Fit and scope
Entities, volumes, revenue model and connected systems, ending in a written scope rather than a proposal deck.
2
Design decisions
Accounts, revenue policy, close calendar and integration map, signed off by your controller.
3
Configure and connect
The ledger is configured and the surrounding systems are connected in a test tenant first.
4
Migrate and reconcile
History and opening balances come across and are reconciled to the prior system, line by line where it matters.
5
Parallel close and handover
One close run with both systems in view, then documentation and training for the team that owns it afterwards.
FAQ
Questions before an implementation
What actually goes wrong in an ERP implementation like this?
Three things, in our experience. Decisions get deferred until after configuration, so the build has to be redone. History is migrated at the wrong granularity, and nobody notices until an audit asks for detail that was never brought across. And the systems either side of the ledger are treated as a later phase, so the first real month-end is the first time anyone tests them together.
Who owns the project internally?
A controller or accounting manager with authority to make policy decisions, plus whoever owns the connected systems. An implementation without a decision-maker on your side stalls, regardless of who implements it.
How much history should we migrate?
Enough to run comparatives and satisfy an audit, at the granularity your auditor expects to test. More is not automatically better: transaction-level history from a system you configured differently can create reconciliation work that never ends.
Can you work alongside our accounting firm?
Yes, and it is common. They own policy and the financials; we own the system, the data and the integrations.
What happens after go-live?
We stay through the first closes. The questions that matter appear in month two and three, when real volume has run through reconciliation and revenue schedules for the first time.
Planning a move to Campfire?
Tell us what you close today and what connects to it. You will get a scoped plan with the decisions listed, not a timeline with a discount attached.