Onda Replay I'm interested
Jira Data Center to Cloud migration

Move to Jira Cloud with zero downtime.

A migration cutover takes days: the JCMA transfer, the post-migration tasks and all the adjustments needed before the Cloud site is handed over. Meanwhile, your teams and your customers keep working in Jira Data Center, and Onda Replay brings every change across to the Cloud. No freeze, no re-keying, nothing lost.

Zero downtime Zero changes lost No issue limit Nothing to install in the Cloud
Your migration, liveIn progress
Jira Data CenterOpen, 214 people at work
Downtime0 minutes
1,248Changes made during the migration
1,236Already in the Cloud
Replayed 1,227 Already there 9 In progress 9 To check 3
Manual re-entry: noneCutover: whenever you choose
Illustration, sample data.
The problem

A migration takes days. Your business doesn't stop.

Copying your projects to the Cloud takes hours, often days. Anything done in Data Center in the meantime (a reply to a customer, an issue moved to "Done", an attachment) never reaches the Cloud. Atlassian ends Data Center support on March 28, 2029: most companies will have to decide how to handle that gap.

Jira Data Center Onda Replay queue Jira Cloud Nothing is captured Transfer starts Transfer ends Cutover Copying existing data ? ? ? ? ? Comment Status New issue Attachment Link

5 changes missing from the Cloud on cutover morning. Nobody has a list to find them.

5 changes replayed in the Cloud, in order, before cutover. Each one has its line in the log.

Freeze Jira

Hundreds of people idle, customers left without answers, and a night or weekend cutover, hoping it all finishes on time.

Re-enter by hand

Hours of double entry, from memory, with no list to check what was missed.

Find out too late

The day a customer, an auditor or a manager looks for the missing comment or status.

What changes for you

Your migration becomes invisible to your teams and your customers.

0

changes lost

Every comment, status change, new issue, attachment or link made during the migration ends up in the Cloud, in the order it was made.

0 min

of downtime

Data Center stays open until cutover. Your teams work as usual, your customers are served, your service commitments are met.

Unlimited

volume

No cap on issues or on changes caught up. A team of 50 or an instance with a million issues: it works the same way.

10:00 am

a daytime cutover

You choose the moment. No more all-nighters or weekend call-outs: cutover happens when it suits you.

Costs avoided

What would the migration cost you without Onda Replay?

Without Onda Replay, you either freeze Jira during the transfer or re-enter everything afterwards. Put a figure on both with your own assumptions.

Your assumptions

What it costs without Onda Replay

Freeze Jira during the transfer€86,6251,575 working hours blocked
Stay open, then re-enter everything€16,5004,500 changes to find and re-enter, or 300 hours. Not counting the ones that get forgotten.
With Onda Replay0 hours blocked, nothing to re-enterFor 250 users, Standard offer: €3,500. Up to €83,125 saved on this migration.

Indicative estimate, based on a 7-hour working day and 4 minutes to find, re-enter and check one change. The calculation runs in your browser: nothing is sent.

Overtime pay

A night or weekend cutover means a team of administrators and contractors paid at overtime rates. With Onda Replay, it happens during the day.

Customers left waiting

A frozen service desk means late requests, missed service commitments, sometimes penalties. With Onda Replay, support keeps answering throughout the migration.

Gaps in the history

A missing decision, approval or time entry means an audit finding or an invoice to redo. With Onda Replay, every change leaves a trace.

Use cases

For teams that can't stop.

Customer support

Your service desk keeps answering throughout the migration. Customer replies and internal notes reach the Cloud, and no request is forgotten.

Product and dev teams

The sprint goes on. New issues, statuses, priorities, assignees and issue links follow in the Cloud, with the same keys.

Time tracking In validation

Time logged in Tempo during the migration is replayed under its author's name. Billing and payroll lose nothing.

Migration partners

Offer your customers a migration without a freeze: daytime cutovers, less rework afterwards, and a log to attach to the end-of-project report.

What is replayed: New issues, same keys Fields and custom fields Statuses Comments Attachments Issue links Tempo worklogs
How it works

Four steps, no downtime.

We prepare together

In 20 minutes, we go over your schedule and your volumes. Your administrator installs Onda Replay in Data Center; there is nothing to install in the Cloud.

Before

Your teams keep going

The migration starts. Onda Replay records everything that changes in Data Center, without slowing anything down for your users.

During the transfer

Everything is replayed

A check flags in advance anything that could get in the way. Then each change reaches the Cloud, in order, with no duplicates.

When you decide

You cut over

Data Center goes read-only, the last changes come through, you open the Cloud. With a record of everything that was replayed.

At cutover
Risk-free

Nothing duplicated, nothing forgotten, everything traced.

Migration logExport
AllTo checkDEMO-12
Made onIssueWhatResultDetail
12/10 09:14DEMO-41CreatedReplayedSame key in the Cloud
12/10 09:16DEMO-12CommentAlready thereAlready copied by the migration
12/10 09:21DEMO-12StatusReplayedMoved to Done
12/10 09:30DEMO-18LinkReplayedDEMO-18 blocks DEMO-41
12/10 09:42DEMO-23FieldsTo checkReporter to set by hand
Illustration, sample data.
  • Never duplicated. What the migration already copied is recognised and not written again.
  • A problem on one issue doesn't stop the others. It is flagged with its reason; everything else moves on.
  • A log for your migration report. One line per change, exportable, with its original date.
  • Nothing slips through. Every 15 minutes, Onda Replay checks that it hasn't missed anything, and alerts you if it has.
Confluence

Confluence too. The same principle, page by page.

Onda Replay for Confluence follows the same method as for Jira: the migration runs with Atlassian's tool (CCMA), your teams keep writing in the meantime, and everything that changes in your spaces is carried over to the Cloud, in order. Migrating Jira and Confluence together? Links between issues and pages follow.

What is replayed

Pages and blog posts: creations, edits (one Cloud version per save), renames, moves in the page tree, moves to the trash, restores and purges.

Attachments: additions, new versions, deletions and restores; a file used in a page is sent before the page.

Comments: page and inline comments, replies, resolving and reopening. If the passage of an inline comment can't be found, the comment is written at the bottom of the page with the passage quoted: nothing is lost.

Labels: additions and removals, on pages, blog posts and attachments, including those set when a page is created; a label already there is not added twice.

Page content: user mentions, links between pages and Jira macros adapted to the Cloud; macros that ship with Confluence are carried over.

Links between Jira and Confluence: an issue that pointed to a Data Center page points to the same page in the Cloud, with no duplicate link.

Third-party app macros (draw.io, PlantUML…) added during the migration: not carried over, replaced by a visible note in the page and listed in Onda Replay so you can add them by hand.

Before and during the replay

  • Onda Replay checks that the service account has every permission it needs on each space, including those granted through a group; if any is missing, the replay pauses.
  • Nothing is written twice: what is already in the Cloud is recognised.
  • Every page written is read back in the Cloud to spot a macro that doesn't display properly.
  • Every replay is kept with all its logs, and can be reopened later.

Onda Replay for Confluence is included in the Advanced offer only. See pricing →

Your data

From your Data Center to your Cloud. Nowhere else.

Onda Replay runs on your side and writes directly to your Jira Cloud. No Onda Replay server in between, no telemetry.

Nothing on our side

Your issues go through no third-party server, neither ours nor anyone else's.

Signed, with its security report

Every release is signed. Its package contains a dated security report and the list of its components.

Minimal access

A dedicated account, limited to Jira, whose secret stays encrypted on your side.

Support without access

To get help, you send us a file you have read, with no secrets in it.

See the Trust Center →

Comparison

Your options for handling what changes during the migration.

Freeze JiraRe-enter by handSync platformOnda Replay
Your teams work during the migrationNoYesYesYes
Changes made during the transferNone, everything is stoppedFrom memory, with no listAs far as the sync rules written cover themAll of them, in order
Cutover timeNight or weekendFollowed by days of reworkOnce the rules are tunedWhenever you want
SetupNoneNone, but hours of data entryRules and scripts to writeOne app, a guided flow
Audit evidenceMigration reportNoneVariableOne line per change
Your data goes through a third partyNoNoDepends on the toolNever
Plainly

What Onda Replay doesn't do.

It doesn't replace Atlassian's migration tool (JCMA). JCMA copies your existing projects; Onda Replay catches up on what changes while it runs.

Dates in the Cloud are the replay dates. The original date stays in the log, and each replayed comment states its author and date.

Changes made outside Jira (directly in the database, some scripts) are not replayed. They are flagged so you can deal with them.

Current version: Jira Data Center 11.3. Jira 10.6 is in validation; clusters are planned but not yet tested.

For Confluence

Replayed content is written by the service account. The original author and date are shown in each page's version history and at the top of each comment, and always in the log.

Replayed pages and comments notify the people watching the page. The Cloud API offers no way to prevent this; the site administrator can turn off notification e-mails during the cutover.

A file deleted from Data Center before the replay has nothing left to send. It is flagged so you can deal with it.

Pricing

One price per cutover, based on your number of users.

One price for the whole cutover, based on your Jira Data Center license tier. No limit on issues or on changes replayed, and the same content at every tier.

Standard

For instances without third-party apps, or whose apps are already covered.

  • The cutover with Onda Replay, preparation included
  • One rehearsal on your test instance
  • 5 hours of assistance
  • Corrective support included

Advanced

For instances that need adaptations: apps, fields, workflows.

  • Everything in Standard
  • Onda Replay for Confluence, included in this offer only, for the cutover of your Confluence spaces
  • Adaptations agreed together during preparation
  • Rehearsals on your test instance, in a number agreed during preparation; beyond that, on quote
  • 15 hours of assistance
  • Corrective support included
Your Data Center licensePrice per cutover
Up to 500 users€3,500€6,000
501 to 1,000 users€5,000€8,500
1,001 to 2,000 users€6,500€11,000
2,001 to 3,000 users€7,750€13,000
3,001 to 4,000 users€8,750€15,000
4,001 to 5,000 users€9,500€16,000

Assistance hours: guidance and answers to your questions during preparation and cutover. Beyond the included hours or the planned adaptations: on quote.

Over 5,000 users, or several instances

Several cutover waves, rehearsals on your test instances, support at each cutover.

Get a quote

For businesses only. VAT not applicable, article 293 B of the French General Tax Code. Migration partners: partner terms on request.

FAQ

The questions people ask before a migration.

Does Onda Replay replace Atlassian's migration tool?

No, it complements it. Atlassian's tool (JCMA) copies your existing projects, users and issues. Onda Replay catches up on everything that changes in Data Center while it runs, right up to cutover.

Do my teams have to change how they work?

No. They keep working in Data Center as usual, right up to cutover.

Is there a limit on issues or changes?

No. Every change made during the migration is replayed, however many there are.

Will Cloud users get notifications?

Replayed changes follow your Cloud projects' notification rules. Onda Replay warns you in advance if a project is likely to send notifications, so you can turn them off during cutover.

Who shows up as the author in the Cloud?

An account dedicated to the migration. Each replayed comment starts with a line naming its original author and date.

Do you see our data?

No. Onda Replay runs in your Data Center and only talks to your Jira Cloud (and to Tempo if you use it). See the Trust Center.

Which versions are supported?

Jira Data Center 11.3, with Jira Service Management and Tempo Timesheets. A version for Jira 10.6 is in validation. Ask us about other versions.

Can we try it first?

Yes. Your team can rehearse the cutover on your test instance before the real one. Tell us you're interested.

What about Confluence?

Onda Replay also exists for Confluence Data Center, on the same principle as for Jira. If you migrate both, links between issues and pages are carried over. See the Confluence section above.

Migration coming up? Let's talk.

Leave your e-mail. We'll prepare a demo around your schedule and your volumes, and we'll tell you first what Onda Replay won't cover for you.

A short form opens in a new tab, with your e-mail already filled in. You can also write to us at contact@alfia-labs.fr.

  • For CIOs and Jira administrators
  • For migration partners
  • No commitment