Trying to Upgrade from old forest v8 to new forest agent v1

Feature(s) impacted

We’re trying to upgrade from the old forest library (v8) to the new forest admin (v1). We created a new project and are following the instructions in the quick start guide. We’re trying to boot up the localhost dev environment and it’s not working. We keep getting a not found, and there’s no logs being registered in the dev console. We created a new project (we’ve been a Forest client for 4 years now) to just to start fresh (we can port over) but when we did that, we don’t see the opportunity to create a new dev environment (so that we can get the dev keys). Overall we’re very confused by the order of events.

Observed behavior

Expected behavior

We’ve upgraded and created new Forest apps several times. What we expected was

  1. Create new project (for the new agent workflow, since we aren’t sure if we can upgrade our current v8 version).
  2. Create dev environment - get the keys we need
  3. Add keys to node.js code
  4. finish dev set up
  5. push to production


  • Project name: ResiDesk-Forest-Agent
  • Team name: ResiDesk
  • Environment name: Dev
  • Agent technology: nodejs
  • Agent (forest package) name & version: agent v1
  • Database type: postgres / sql
  • Recent changes made on your end if any: created a new project

Hello @Alexander_Holman,

We’re thrilled to see that you’re moving forward to the new forest agent. We have created a step by step guide to help you complete the migration. I hope that you will find this useful.

The confusion you are facing with your new deployments is because all new onboardings are by default done on our Cloud solution. The agent is hosted by us and we handle everything, you just have to configure your database connection via the UI. You can find out more about it in our documentation dedicated to Cloud.

Best regards,

1 Like