If I were to create a test workspace and work on a resolution and custom bots, can I migrate this over to a production workspace? If so, what are the limitations of migrating between workspaces?
Best answer by Milan
View original
Userlevel 4
+5
I do not think it is possible - which makes developing things within TEST workspace unnecessary (at least for some light things).
Â
Â
That's something that is urgently needed. I believe I've already mentioned this in some discussions with Intercom people but it's good that is brought up here too and let's tag @Product Wishlist​ to see it 
Â
One more thought on this would be to allow PRODUCTION to be copied to TEST, same as what developers do when they want to develop new stuff, they branch out the copy of production and make it their development branch for the feature they are working on.
Â
Â
Also looking for this, would be great to test comms on staging before putting them live.
Â
@Product Wishlist​  Manually transferring from TEST is a PITA
As the person most responsible for bringing Intercom into my company, this missing feature really makes me look bad. Intercom looks like it is not experienced in working enterprise environments. I don't understand how so many large enterprises seem to use this product without the most basic ability to develop and test in lower environments -- then safely package it up to deploy/migrate to a prod environment.
Â
It makes it pretty easy to mess up customer experiences since you have to 'build' content and behavior in production. The least Intercom could do is provide some way to print out the metadata of a configuration in a TEST workspace so it would make the manual recreation in PROD easier and less error prone. Right now I am copying text and making screenshots.
Agreed,
Â
I also have had issues with extra characters when copy/pasting from TEST to prod (^&%^ on the end).
Â
So not only can we not simply migrate TEST-Prod there are chances of typo's as well as copypasta issues as well.
Â
Migrating seems like it would be a simple process to implement and maintain the buttons, copy, and logic.
Not possible based on a recent Intercom Chat
This is a huge pain, especially when managing multiple Intercom instances.
It pretty much forces us to either spend a lot of time duplicating settings and recreating automations or make changes directly in production which is obviously risky.
We are going with a mix now which is far from ideal and causes plenty of headaches.
Reply
Join the Intercom Community 🎉
Already have an account? Login
Login to the community
No account yet? Create an account
Intercom Customers and Employees
Log in with SSOor
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.