A question lands from your biggest customer that your carbon accounting platform can't answer. Your auditor asks where a Scope 3 number came from, and the trail ends at a spend category and a factor nobody can source. You open a support ticket and reach a product specialist, not a climate expert.
At that point, most sustainability and finance leads ask the same thing: is it time to switch carbon accounting platforms, and what might break if we do?
Switching is very manageable, but it is not a simple data export. A migration moves your methodology, emission factors, and the audit trail behind every disclosure you've already made elsewhere. Get those right, and the new platform starts on solid ground. Get them wrong, and you can end up restating a baseline you've already shared with customers, CDP, or regulators.
Here is what actually happens when you switch, and what to check before you make the decision.
Why do companies switch carbon accounting platforms?
It's rarely for features alone. The common triggers:
- No expert behind the software. Support can explain the interface, but not whether your methodology holds up, and you need an in-house expert to use the tool.
- Questions the platform can't answer. SB 253 moves to limited assurance on Scope 1 and 2 in 2027, and more customers are sending CDP and EcoVadis requests. Some tools are not designed for auditing and answering questionnaires.
- Scope 3 has outgrown the tool. Spend-based estimates worked for year one. Customers now want supplier-specific data.
- A tool that still needs an operator. Many teams bought software expecting a solution and got something that still needs a carbon accountant to run. We cover that trade-off in Carbon Accounting Software vs. DIY vs. Expert Guidance.
Will your emissions numbers change when you switch?
Almost certainly. What matters is why. Small shifts usually come from:
- Different emission factor sources or source years
- Inflation adjustments applied to spend-based factors
- Different global warming potential (GWP) values, such as IPCC AR5 versus AR6
Larger gaps usually point to different assumptions, materiality thresholds, or calculation methodology. Some changes are plain errors from your old inventory or from the switch: unit-of-measure mismatches, or fields that didn't map cleanly on import.
Your new provider's job is to document and explain every material difference during a migration before anyone outside the company sees it.
Does switching platforms mean restating your baseline?
Not automatically. The GHG Protocol Corporate Standard expects companies to recalculate base-year emissions when a methodology change, structural change, or discovered error significantly affects the base year. It leaves "significant" to each company's own recalculation policy.
If you have a science-based target, SBTi applies a 5% threshold: a change of that size in base-year emissions triggers target recalculation.
A migration that only updates factor vintages may stay under the significant threshold. One that moves a large Scope 3 category from spend-based to activity-based data probably won't. Either way, recalculating is a methodology decision, documented in a policy. No platform makes it for you. If a target is affected, our target setting team can assess whether it still holds.
Does your methodology have to change?
It shouldn't change by accident. Before migrating, compare methodology category by category, especially for Scope 3. Whether a category uses supplier-specific, activity-based, or spend-based data shapes every future result and your year-over-year comparison.
Then check if the new platform uses the data you already collect, such as meter-level versus site-level energy data, fuel types, or distance and weight for freight. A good migration reuses existing data wherever possible instead of forcing a new round of collection on your team.
What data can you actually take with you?
This is where migrations fail most. Category or scope summaries are useless. You need exports at the source-record level, including:
- Raw activity data and where it came from (invoice, meter, system)
- The emission factor applied to each record, with its source and version
- Scope and category assignments
- Attached evidence files and change logs, which your assurance provider will want
If the current platform has an "export all" function, use it. If not, find out what can be pulled, and at what level of detail, before you give notice. Then check your contract or service agreement for what data you're owed on exit and whether the vendor charges a migration or export fee.
Should you re-import results or recalculate everything?
Usually both, for different years. Importing prior-year calculated results directly preserves the numbers you've already disclosed and the audit trail behind them. That matters most when the two platforms barely overlap.
For the go-forward inventory, review activity data source by source. Decide what imports cleanly and what needs transformation first.
Will your assurance survive the migration?
It can if you can ensure all of your data is traceable: can an auditor still drill down to the source document, the activity value, the emission factor (with source and version), and the change history? Establish whether that happens inside the platform or through an audit export.
Then confirm the practical details:
- What access will your auditor get to the platform?
- Does the service agreement include support for auditor questions?
- Is that support built into platform fees, or billed separately?
For SB 253 filers, this is not a future concern. Limited assurance on Scope 1 and 2 starts in 2027, so the platform holding your current data has to stand up to an assurance provider's review. If it doesn’t, you should switch to one that does ASAP.
What should the new platform do better?
Use the switch to close gaps and improve your inventory, not just to copy the old setup. Two areas to check first.
Scope 2 dual reporting. The GHG Protocol Scope 2 Guidance requires both location-based and market-based totals wherever contractual instruments are available. The platform should:
- Calculate both methods from the same activity data, in parallel
- Show how it applies the market-based hierarchy
- Account for RECs and renewable energy purchases
- Use residual mix factors from recognized sources, not location-based grid factors by default
Scope 3 coverage. Check which of the 15 categories the platform supports. Upstream categories 1 through 7 need flexibility to take spend, activity, or industry-average data. Downstream categories 8 through 15 vary far more by industry, so the platform needs a way to assess which are material and how to calculate them.
Also check whether it can collect supplier-specific data directly, or use supplier data from sources such as CDP. And confirm it can mix methods within one category, for example, weight-based for some purchases and spend-based for the rest. Our supplier engagement work starts from exactly this question.
When is the best time to switch carbon accounting platforms?
Between finishing one full-year calculation and starting data collection for the next. In that window, you can assure, disclose, and report the completed inventory from the old system while the migration runs alongside it. Never switch mid-calculation or in the middle of a data refresh.
Two timing traps catch people:
- Renewal notice periods. Many software contracts auto-renew unless you give notice before the term ends. Read that clause before you start evaluating, not after.
- Submission deadlines. If a CDP, EcoVadis, or SB 253 submission depends on this year's numbers, finish it on the platform that produced them.
How long does a platform migration take?
Typically two to six months, depending on data volume and complexity. Scope 1 and 2 across a handful of sites sits at the shorter end of that timeline. A multi-entity inventory with a full Scope 3 build sits at the longer end.
The longer the two platforms overlap, the better. Parallel running leaves time to export data, recalculate, reconcile differences, train staff, and adjust data feeds before the old contract ends.
A realistic migration runs in six steps:
- Export everything the current platform holds, at the source-record level.
- Compare methodology category by category, and document every change.
- Map and import prior-year results and current activity data.
- Recalculate and reconcile new results against old ones, explaining every material difference.
- Apply your recalculation policy to decide whether the base year moves.
- Confirm the audit trail with your assurance provider before cutting the platform you are switching from.
Your team supplies data access and decisions. Expert support does the mapping, reconciliation, and methodology work.
Switching platforms is a methodology decision
Migrations that go badly rarely fail on export formats. They fail because nobody owned the methodology: which factors, which Scope 3 method, whether the base year moves, and how to explain the difference to an auditor. Software can calculate your new totals. It can't make those judgment calls.
That's why Good.Lab pairs its carbon accounting platform with sustainability experts who run the transition: exporting and mapping your history, reconciling the numbers, documenting methodology changes, and keeping your assurance trail intact.
If your renewal is coming up, or your current platform can't answer the questions your customers and auditors are asking, talk to Good.Lab about a managed transition.
