.webp)
Migration & delivery
Banking Migration: Move What Matters
Preserve the rest. A governance-led migration from Asana, Smartsheet and ServiceNow to Atlassian.
01
The challenge
Moving platforms did not mean moving every record.
A banking organization worked with Avaratak to migrate from Asana, Smartsheet and ServiceNow into an Atlassian environment spanning Jira Service Management, Assets, Confluence and Jira.
The environment included 200 Jira Service Management agents, more than 32,000 assets, 2,000 Confluence users and 2,000 Jira users. The challenge was to bring over the information pertinent to the new environment without turning the migration into a wholesale copy of the past.
The central decision was not simply where to put the data. It was which information belonged in the working platform and which should be retained separately. A record could still be worth keeping without needing to become part of the live Atlassian environment.
Avaratak's governance-led Atlassian consulting put that distinction at the center of the migration.
02
Our approach
Governance determined the migration scope. Rather than treating every record in the three source platforms as a migration requirement, Avaratak used governance to identify the pertinent information to bring forward.
Separate migration from retention
The approach established two destinations: pertinent information moved into Atlassian; the remainder of the Asana, Smartsheet and ServiceNow data was retained on a server that was then kept powered off.
This was a deliberate separation between the working environment and the historical archive. Information did not have to be loaded into the new tools simply because it existed in the old ones, and information outside the migration scope was not discarded.
Make the boundary clear
For this engagement, the important distinction was needed in the live environment versus retained outside it. That kept the migration focused on pertinent information while giving the remaining legacy data a separate place.
Move what matters. Preserve the rest.
03
What we built
- Jira Service Management for 200 agents The service-management component of the banking organization's Atlassian environment.
- More than 32,000 assets in Assets Asset information within the same Atlassian environment as the service-management platform.
- Confluence for 2,000 users The knowledge and collaboration component of the environment.
- Jira for 2,000 users The work-management component of the environment.
- A selective migration from three platforms Pertinent information brought forward from Asana, Smartsheet and ServiceNow, with governance determining what belonged in the new environment.
- A separate, powered-off archive The remaining source-platform data retained on a server kept powered off, outside the live Atlassian environment.
04
The results
The result was an Atlassian environment with a deliberate boundary between working information and retained legacy data.
- Pertinent information brought forward Migration scope followed governance decisions rather than a requirement to copy everything from the three source platforms.
- Legacy data retained, not discarded The remainder of the Asana, Smartsheet and ServiceNow data was kept separately on a powered-off archival server.
- Four Atlassian products in the resulting environment Jira Service Management, Assets, Confluence and Jira supported the reported footprint: 200 agents, more than 32,000 assets, and 2,000 users each for Confluence and Jira.
The Avaratak take
The value of a migration is not the volume of data moved. It is the judgment behind what moves, what stays available in the working environment, and what is retained elsewhere. In this banking engagement, governance made those choices part of the migration itself.
Planning a similar move? Start with a 30-minute migration conversation about what belongs in your next environment and what should be retained separately.
05
In their words
Move what matters. Preserve the rest.
Decide what should move before you migrate
Bring us your source systems and the decisions you need to make. Avaratak's senior Atlassian consultants will help you shape a migration around the information your organization actually needs.