Data transition from evaluation to production

Question

Hi all,

I'm new to this community.

Current status:

- We're using Jira, Confluence etc already on-premise, but still OTRS as ticket system. My company wants to migrate the on-prem Atlassian stuff to the cloud and additionally, my task is to move from OTRS to Jira Service Managemnt (JSM).

- So, as a pilot project, I'm creating a JSM site in the Atlassian cloud (already working to some extent) - let's call it company-evaluation.atlassian.net

- Once processes are polished, I want to invite a "pilot-customer" to this JSM. This customer will create tickets etc in a productive way.

Now, I want to know:

Q1) Once the pilot is over and ALL of our customers shall migrate to JSM (coming from OTRS6, btw), will all the pilot-customer's tickets remain or do I need to start from scratch?

Q2) Let's assume that the URL will change from company-evaluation.atlassian.net to company-production.atlassian.net. Is that URL change possible when going live? Or would I need to move all data from company-evaluation to company-production?

Q3) Would the pilot phase (with a real customer and real "agents") require me to get into "paid mode", already?

Answers are highly appreciated. :-)

Thanks,

Horst

unknown · Answer

Thx for the info. Alright, then. Next questions arise (if you're not tired):

Q6) To stay under the hood of the above-mentioned "migration licensing", the JSM would need to remain "unproductive" until the complete on-prem-2-cloud migration is done, right?

Q7) Let's assume that I get a separate JSM instance to be productive. Is there a good way to "merge" it later with another instance, into which we separately moved our on-prem Atlassian data into the Atlassian cloud?

i.e. to keep things separated we would have, with current planning:

Instance A: only used for JSM, to become productive "soon" (say: next 3-6 months)

Instance B: only used for migrated on-prem stuff (say: 6-12 months)

Is there a good way to do "A+B"? There's probably some disadvantages by having two of those "instances" (duplicate user registries, process fiasko maybe, etc)

Tessa Tuteleers · Answer

Hi again @[deleted],

yeah, the thread is better if you keep them together under one answer, but I'll continue here to keep ik together.

Since you are basically first setting up a cloud environment for migrating OTRS -> JSM and then going live with that while migrating you jira server instance, I don't think this falls under the migration licensing. And even more, you would be testing a migration on a live instance, with possible impact on your production JSM. I would advice against that.

But I think that you should perhaps direct your questions to Atlassian themselves, as they can assess the situation and give you all the posibilities they see.

Hope you have a smooth transition!

Happy Easter!

- Tessa

unknown · Answer

oops, my reply to your reply appeared as a new "answer"... :-(

So, please see my answer above with Q4 and Q5. Thx :-).