A handful of CDM-registered afforestation and reforestation projects, facing a mechanism that stopped accepting new registrations and an increasingly thin buyer base for CDM-era credits, chose to carry their activity into the VCS program instead of winding down. That move is not a relisting — Verra does not simply adopt a CDM-era baseline and keep issuing. It is closer to a re-validation against a different methodology, with the CDM history treated as useful supporting evidence rather than a substitute for VCS requirements.
Why a Straight Transfer Doesn't Work
CDM and VCS AFOLU methodologies diverge on enough points that a CDM-era baseline cannot simply be relabeled. Non-permanence treatment is the clearest example: CDM AR used temporary credits with built-in expiry, a model VCS does not use at all — VCS uses a buffer-pool deduction instead, which has to be newly calculated using VCS's own risk-rating tool rather than inherited from the CDM filing. Monitoring and remote-sensing expectations have also moved on considerably since most legacy CDM AR projects were originally designed, so a monitoring plan written a decade or more ago typically needs updating to meet current VCS requirements even before any baseline question is addressed.
What the Transition Actually Requires
| Step | What changes |
|---|---|
| Methodology mapping | Confirm which current VCS AFOLU methodology covers the project's activity type |
| Baseline re-assessment | Re-run baseline-setting under the VCS methodology's own rules, using the CDM baseline as a reference point, not a substitute |
| Buffer pool calculation | Apply VCS's non-permanence risk tool; CDM temporary-credit treatment does not carry over |
| Monitoring plan update | Bring monitoring up to current VCS requirements, often adding remote-sensing components |
| Re-validation | Full validation against the applicable VCS methodology, not a review of the prior CDM validation |
The CDM project's historical monitoring data is genuinely useful here — multi-year field measurements and growth records from an already-running project are hard to manufacture retroactively and give the VCS validation a stronger evidentiary base than a brand-new project would have. But usefulness as evidence is different from automatic acceptance; the VVB validating under VCS is validating against VCS's methodology, and has to independently assess whether the historical data supports the baseline and stocking claims the new filing makes.
What Doesn't Transfer at All
A project's CDM registration number, its CDM crediting period, and any CDM-issued credits already retired or sold stay exactly where they are — they do not migrate with the project. The transition is prospective: it governs how future removals are credited going forward under VCS, not a retroactive reclassification of CDM-era issuance. Buyers holding CDM-era credits from the project's earlier crediting period are unaffected by what the project does afterward under a different standard.
Why a Project Bothers
The practical driver is almost always buyer access. CDM credits (Certified Emission Reductions) have a narrower compliance-market use case than they once did, and most voluntary-market buyers today transact in VCS or equivalent voluntary units, not CERs. For a project with real, ongoing forest growth and genuine monitoring history, re-platforming onto VCS is often the more defensible path to continued revenue than attempting to find buyers for a legacy instrument whose market has substantially narrowed — provided the re-validation work described above is actually done, rather than assumed.
Turn climate goals into a verified portfolio
TREEO connects the full carbon cycle — eligibility, simulation, real-time monitoring and registry-ready reporting — combining expert consulting with dMRV technology so the evidence exists before anyone asks for it.



