# How to deal with client that doesn't know how to use Trellis/Bedrock/Sage?

**URL:** https://discourse.roots.io/t/how-to-deal-with-client-that-doesnt-know-how-to-use-trellis-bedrock-sage/25407
**Category:** trellis
**Tags:** sage9, trellis
**Created:** 2023-05-23T14:57:16Z
**Posts:** 5

## Post 1 by @kurt — 2023-05-23T14:57:17Z

I am using Trellis/Bedrock/Sage for all the WordPress projects in my agency, and I am in love with the roots environment.  
From time to time a client decides to leave us and wants to take control of their website, but without knowing anything about Trellis/Bedrock/Sage, they are stacked.  
I am pretty sure the same thing happened to others, so I am wondering how you dealt with this situation?

1. what are the steps to migrate from Trellis/Bedrock/Sage to a different/simple/common wordpress scenario?

2. what did you say to your client when they “accused you” that this is not a WordPress website and it is too complex and they can’t work with it?

it would be good if you could share your similar stories and how you dealt with this.

thanks

---

## Post 2 by @csorrentino — 2023-05-23T17:44:37Z

I have limited experience with Trellis so I can’t offer suggestions for that, but there are a few threads here about migrating from a bedrock structure to a standard wordpress install. Here’s one place to start:

> [@I want to change a roots/bedrock installation back to Wordpress](https://discourse.roots.io/t/i-want-to-change-a-roots-bedrock-installation-back-to-wordpress/21147):
>
> I’m migrating websites from 1 host to another, and the 2nd host doesn’t accept bedrock installations. Now I want to change the roots/bedrock installation and make it a Wordpress installation. What I did: Created new Wordpress installation Moved all the Bedrock app/ content to wp-content (themes, plugins, mu-plugins, uploads and more) Gave it the old database and changed the wp\_options to the new .test link Edited wp-config.php to have the correct local settings. It ran locally, but after imp…

This manual method may be one of the simplest methods:

[https://discourse.roots.io/t/how-to-move-a-site-away-from-trellis-bedrock/16796/4?u=csorrentino](https://discourse.roots.io/t/how-to-move-a-site-away-from-trellis-bedrock/16796/4)

What does your client want to work on? The theme or do they only want to manage plugins and wordpress updates?

---

## Post 3 by @MWDelaney — 2023-05-23T19:51:38Z

I often run into this problem when clients move away from agencies I’ve worked with. I’ve written a [GitHub Workflow](https://github.com/MWDelaney/trellis-github-deployment/blob/e2365ccae35b7e88d787a892f2e8d2a53dc5d3c0/.github/examples/eject-production.yml) (which calls [an action](https://github.com/MWDelaney/trellis-github-deployment/blob/e2365ccae35b7e88d787a892f2e8d2a53dc5d3c0/.github/actions/eject/action.yml)) which essentially performs the manual steps the comment @csorrentino linked. It might need some tweaks for your setup, but maybe it would help!

---

## Post 4 by @Tim — 2023-05-24T10:31:14Z

Number one. Having it written in the job quote AND your general terms and conditions. Describe what tools you use and why you use it over a simple installatron WP install. The client signs the job quote, knowing the deeds.

you can describe something like, we use a open source products from Roots. It renders a wordpress website, like you are used to. Only that for us is more efficient, flexible (and maybe cheaper) to roll out fantastic website for you, etc. Please know that this website only runs on this and that.

idk, a quick suggestion.

---

## Post 5 by @joshb — 2023-05-24T17:10:45Z

I usually just tell them they’re making a big mistake and explain why and they say, “ok, nevermind” and stay. Otherwise, I explain the process of switching and the costs associated and they say the same thing.