Forums for the Business Analyst

  Modern Analyst Forums  Business and Sy...  Data Analysis f...  Data migration user story writting
Previous Previous
Next Next
New Post 4/22/2019 10:59 PM
User is offline Ash 02
2 posts
No Ranking

Data migration user story writting 

I have recently started working as a BA, my role is to capture user stories related to data migration from legacy to new. 
I need help with some sample user stories for data migration. 

For example if abc screen data from legacy system is migrated and as new system user i want to view the transferred data on xyz screen. 

Note: the purpose right now is to view the migrated data. so i am confuse with how to write what benefit the user story will add.

Thanks in Advance!!


New Post 8/2/2019 2:19 AM
User is offline Stewart F
55 posts
8th Level Poster

Re: Data migration user story writting 

Hi Ash, 

As part of your tasks carried out so far, have you mapped what data will go where? For example, the 'Client Address' field in Legacy system will map to 'Primary Client Address' field in New system.

This data mapping will be crucial to the success of your task. Developers etc will need to know where all the data goes. You could write a User Story for each and every field, and without knowing how many of them there are its a little hard to advise, but I would complete a table in Excel or something similar. Have one column which states what the Legacy field is called, another stating what its format is (is it alpha characters only for example), the next column says what the maximum character length is in legacy system. The do the same column, but for the new system.

You will need to make sure that the new system fields at least match the old fields, otherwise yo wont be able to move the data over (you'll get errors all over the place). You may need to speak to stakeholders to find out how long they want fields and what sort of data is to be entered into the fields (just alpha, alpha & Numeric etc.).

Then, once that exercise is complete I would speak to the developer who is doing the data migration, and see how he/she wants to split the User Stories out. Do they want just one User Story, or multiple? Create the User Stories as advised by your Developer and make sure you attach the Mapping table to it, so that the Developer can relate to it. 

Previous Previous
Next Next
  Modern Analyst Forums  Business and Sy...  Data Analysis f...  Data migration user story writting

Community Blog - Latest Posts

Heta Raval
Heta Raval
In a current scenario, when you are eliciting software service-based requirements then, you may be able to derive requirements in certain varieties. In the beginning, they can be just functional or non-functional requirements. But when you come across many other requirements as time goes, you can conclude requirements into several categories and wi...
0 Responses
Heta Raval
Heta Raval
It is essential to write an impressive approach which helps you to make a client convinced about your understanding of his requirement. The satisfactory approach would help you to be on the same page with the client. So, your chances to get the contract/project would raise. In order to provide a technical solution, a business analyst needs to recog...
2 Responses
Machine Learning (ML) models are intended to positively impact business efficiency. By understanding how these models are created, how they function, and how they are put into production, one can fully utilize their potential to make a difference in every day scenarios.   What is a Machine Learning Model? By creating cases within a narrow d...
0 Responses

Latest Articles

Six Estimation Safety Tips
Oct 13, 2019
Estimation is a chronically thorny issue for software practitioners. Most people need to prepare estimates for the work they do, but in our industry w...
Copyright 2006-2019 by Modern Analyst Media LLC