Answered Migration -> Local to Remote // One server to another // Duplicating MODX sites

After evaluating MODX for about a month, we've decided it's the CMS for us.
Now there's a couple of services we provide, and I'm wondering how to set up the best work-flow for working with MODX.

Moving MODX site local to remote
Sometimes client doesn't have hosting space yet, so we start building locally.
How does it work when copying local site to clients hosting server, and pitfalls to take into account?

Moving MODX site from one server to another
Actually pretty much the same question as the first.
Is it as easy as setting up a new mySQL database at new server and copying files/importing saved template?

Duplicating MODX sites
For some services we pretty much want a general template that we can apply again and again for different clients.
So we'd create a template site in MODX, and then deploy that and start customizing it as per client.
Is it possible to copy sites withing MODX from one to another?

Both Vapor and Teleport would work for what you want. Vapor will sometimes have trouble with large sites, and Teleport is somewhat more complicated to set up the first time.

For your template sites, another option would be to use MyComponent to create a package containing the things you want to add or modify. Then, at a new site, you'd just install a fresh copy of MODX and then install your custom package.

BTW, one thing to avoid when moving a whole site is transferring the files individually with FTP. That often results in missing and/or corrupted files and problems that are difficult to diagnose.