Alderstone Customer Move Tool - reinventing ITSM data migration
Hi Everyone, For those of you that have been frustrated by trying to move data, cleanly upgrade or consolidate ITSM systems we at Alderstone would like to invite you to take a look at our Customer Move Tool (CMT) which has just been released. At last there is a way for you to manage and migrate your ITSM data quickly and safely. No more waiting, no more spreadsheets; with CMT you can move all your data from one ITSM instance to another in less than a day! As the focus for ITSM moves to the Cloud we can help with this transition too, with no need to leave any historical data behind. For more information please visit http://alderstone.com/cmt/ we're running some webinars where we will discuss the benefits of CMT and a technical demo we'd love you to join us, please register at http://alderstone.com/cmt-events/ If you can't make the sessions or want more information, please contact us c...@alderstone.com Thanks Sean ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: RRR|Chive vs. DDM
Hi Lyndsay Apologies for the length of the post, it isn’t a simple question to answer. I have previously used both DDM and RRRchive. While RRRchive has some great improvements in terms of handling the deletion of data and configurability, the main issue you're likely to face is performance. The Remedy API is great at a number of things, but bulk data migration is not among them. Using RRRchive, it previously took us over thirty days to accomplish a full data migration from a full copy of a Production system. After that migration, we then had to perform multiple delta migration runs leading up to go-live. The inherent limitation of the Remedy API has been recognised by BMC, and for the DDM product, some Forms like Audit and Worklogs are now migrated at the database level. Your approach of creating a new environment, rather than upgrading-in-place is one with a lot of advantages; with a fresh install you can be confident that all ITSM modules have been installed cleanly and you can fully test the environment prior to the cutover - I really prefer this approach. Unfortunately the challenges of moving all the data has put some companies off. In response to these challenges, we, at Alderstone Consulting, have spent the last two years developing a powerful data migration tool specifically for the BMC ITSM platform. It’s really good at migrating data for the kind of parallel environment upgrade you're performing, as well as other data migration tasks. Our website at www.alderstone.com/cmt has a lot more information. In summary, our tool has a number of advantages over other tools currently available; 1. Moves data at the database level - we are typically able to move an entire ITSM application within a single day, rather than several weeks. The final delta migration for the Production cutover is less than an hour. 2. Automated discovery and analysis - CMT will discover a Remedy application including customizations and map the data. Any discrepancies like mismatched field lengths, missing enums or missing fields are identified and presented in the CMT Workbench web UI. This is a distinct advantage over other tools, which require you to mess about with XML files and will not automatically identify differences or pick up customisations. For a lightly customised system we would typically be ready to move data within a couple of days - which believe me compares very favourably to the effort expended in previous upgrade projects I've been involved in! 3. Relationship Aware – while other tools migrate on a simple form-by-form basis, CMT builds a data model of your Remedy application which it uses to migrate data.. This opens up a number of capabilities such as being able to migrate individual ITSM companies between Remedy systems, consolidating multiple Remedy systems into a single multi-tenancy system, performing archiving of data during data migration, etc. 4. Flexible and Powerful Mapping and Transformation– using the CMT web user interface you have full control over the way data is migrated and can transform and map data to handle a range of scenarios, including populating new fields with defaults, transforming Product Catalog data, selectively mapping data to new Forms, fields or entities. In fact, CMT would support all of the Remedy-to-Remedy cases Ben Cherny’s identified. Finally CMT handles data deletions, has outstanding exception management (no more searching through log files) and very good operational capabilities Please let me know if you'd like to discuss this further ( sean.harries@alderstone,com) or you could sign up for one of our webinars at http://alderstone.com/cmt-events/ We will also be at BMC Engage next week, please look for us on the KTSL stand at #509. Cheers Sean *Sean Harries* Alderstone Consulting Ltd Revolutionise your management of BMC Remedy ITSM Services with CMT http://alderstone.com/cmt/ Mobile: +44 (0)7976 558048 Skype: seanharries MSN: seanharr...@alderstone.com sean.harr...@alderstone.com e-mail: sean.harr...@alderstone.com Linkedin: http://www.linkedin.com/in/seanharries On 7 October 2014 15:42, Ben Chernys ben.cher...@softwaretoolhouse.com wrote: ** There is also Meta-Update http://www.softwaretoolhouse.com/ and specifically the ITSM 7.1 Migration Package http://www.softwaretoolhouse.com/product/PkgMigItsm/index.html of scripts which allows you to change your companies, organization, people, support structure, product catalogue – and even Changes of type Release into Releases – along the way. No it is not free but the costs are small compared to the efforts saved. Contact me off list for more details or trials. Cheers Ben Chernys Senior Software Architect [image: logoSthInc-sm] Canada / Deutschland Mobile: +49 171 380 2329GMT + 1 + [ DST ] Email: *Ben.Chernys_AT_softwaretoolhouse.com Ben.Chernys_AT_softwaretoolhouse.com*Web: www.softwaretoolhouse.com We are a BMC Technology Alliance
Re: Ticket Data Migration from 7.5 to 8.1
Hi Kiran, Jarl, Listers, While RRRchive has some great improvements in terms of handling the deletion of data and configurability, the main issue you're likely to face is performance. If you are able to agree the data freeze and data catch up management around a 20 day delta process then that is OK. On many of our projects, we found that was difficult to agree with the business and stake holders so we developed the Customer Move Tool. The Remedy API is great at a number of things, but bulk data migration is not among them. Using RRRchive, it previously took us over thirty days to accomplish a full data migration from a full copy of a Production system. After that migration, we then had to perform multiple delta migration runs leading up to go-live. The inherent limitation of the Remedy API has been recognised by BMC, and for the DDM product, some Forms like Audit and Worklogs are now migrated at the database level. The CMT Tool has a number of advantages over other tools currently available; 1. Moves data at the database level - we are typically able to move an entire ITSM application within a single day, rather than several weeks. The final delta migration for the Production cutover is less than an hour. 2. Automated discovery and analysis - CMT will discover a Remedy application including customizations and map the data. Any discrepancies like mismatched field lengths, missing enums or missing fields are identified and presented in the CMT Workbench web UI. This is a distinct advantage over other tools, which require you to mess about with XML files and will not automatically identify differences or pick up customisations. For a lightly customised system we would typically be ready to move data within a couple of days - which believe me compares very favourably to the effort expended in previous upgrade projects I've been involved in! 3. Relationship Aware – while other tools migrate on a simple form-by-form basis, CMT builds a data model of your Remedy application which it uses to migrate data.. This opens up a number of capabilities such as being able to migrate individual ITSM companies between Remedy systems, consolidating multiple Remedy systems into a single multi-tenancy system, performing archiving of data during data migration, etc. 4. Flexible and Powerful Mapping and Transformation– using the CMT web user interface you have full control over the way data is migrated and can transform and map data to handle a range of scenarios, including populating new fields with defaults, transforming Product Catalog data, selectively mapping data to new Forms, fields or entities. Finally CMT handles data deletions, has outstanding exception management (no more searching through log files) and very good operational capabilities Please let me know if you'd like to discuss this further ( sean.harries@alderstone,com) or you could sign up for one of our webinars at http://alderstone.com/cmt-events/ Cheers Sean *Sean Harries* Alderstone Consulting Ltd Revolutionise your management of BMC Remedy ITSM Services with CMT http://alderstone.com/cmt/ Mobile: +44 (0)7976 558048 Skype: seanharries MSN: seanharr...@alderstone.com sean.harr...@alderstone.com e-mail: sean.harr...@alderstone.com Linkedin: http://www.linkedin.com/in/seanharries On 17 November 2014 18:14, Jarl Grøneng jarl.gron...@gmail.com wrote: ** Hi We'r in the same process. 150Gb data, estimated 20 days in initial transfer using rrrChive. Nest load will take next to nothing. -- J 2014-11-15 8:10 GMT+01:00 Kiran Patil kiranpatil@gmail.com: ** Hi All, We are doing upgrading customer Remedy 7.5 to 8.1 Here is background - 1. Customer has 750GB-800GB transnational data of Incident, Change, Problem. 2. We are not doing in-place or staged In-Place upgrade. We will implementing new 8.1 system and migrating data from Remedy 7.5 to Remedy 8.1. 3. Core Req: 1 - Customer wants all historical data to be migrated into Remedy 8.1 along with work logs (with attachments), Related other tickets, task, SLA, Approvals (For change), audit log. 2 - Customer wants to retain old ticket number in system and dont want new ticket Id to be generated during migration process. Our Solution: 1. Using UDM we can import transaction data and disable new Id creation and can retain old ticket number however we cannot control on C1 to retain from old system. UDM approach has 64000 records limitation per batch so migrating 750GB will take months or may be years to migrate data. Is anyone has migrated ticket data using this approach, I would like to hear issues/challenges occurs during activity. As per BMC somehow they dont recommend it. Any suggestion or idea will be welcomed. Thanks Kiran Patil -- *Regards* *Kiran PatilMobile: +91 9890377125* _ARSlist: Where the Answers Are and have been
Re: Upgrade to 8.1 AR/ITSM
Hi Kathy, for an older version of ITSM like yours we would recommend a new instance of ITSM 8.1 rather than any upgrade in place. With a clean install you will know that you have only taken the customizations that you really need rather than legacy bug fixes and code that has been superseded by ITSM 8.1. A clean 8.1 install will generally be faster, easier to support and of course easier to upgrade to the next ITSM version. You will of course still need to review the customizations you have applied to your current system and decide what you need to retain, but that is of course best practice with an upgrade anyway. As for the data, you will want to migrate over the foundation data, and the transactional data onto ITSM 8.1 . This is an ideal time to clean up data and potentially archive some of the tickets that you no longer need direct access to. We use our Customer Move Tool (more info http://www.alderstone.com/cmt) for this, as we can migrate all modules data or a reduced set, depending on your requirements. In general we've been able to move all data within one day and the upgrade process becomes very smooth indeed. Please let me know if you would like to talk about this in more detail or I can set up a Demo of our migration tool to show you the flexibility and power of the application. regards Sean *Sean Harries* Alderstone Consulting Ltd Revolutionise your management of BMC Remedy ITSM Services with CMT http://alderstone.com/cmt/ Mobile: +44 (0)7976 558048 Skype: seanharries MSN: seanharr...@alderstone.com sean.harr...@alderstone.com e-mail: sean.harr...@alderstone.com Linkedin: http://www.linkedin.com/in/seanharries On 13 January 2015 at 07:39, Patil, Vivek vivek_pa...@bmc.com wrote: ** Hi Kathy, Do you have customizations on CORE AR forms ? Planning the upgrade : https://docs.bmc.com/docs/display/public/itsm81/Planning%20the%20upgrade All information on upgrades : https://kb.bmc.com/infocenter/index?page=contentid=S:KA400850 Thanks, Vivek *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *KathyMorris *Sent:* Tuesday, January 13, 2015 12:44 AM *To:* arslist@ARSLIST.ORG *Subject:* Upgrade to 8.1 AR/ITSM ** Hi, We are upgrading from 7.0.3 ITSM /AR 7.5 (highly customized) to 8.1. I would like to find out from other experts – which approach would you take? A) A new 8.1 install and copy objects over after converting the custom code to overlays or B) Copy over point database and point to the new instance? upgrade in place? We have a preference already, just want to confirm. Also, what are some gotcha’s that we need to look out for. I have been doing lots or reading, however I want to make sure this upgrade runs as smooth as possible so your feedback is appreciated. _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: Where the Answers Are and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Upgrade ITSM from 7.6.04 SP3 to 9.0.01
I would completely agree with David here, new environment clean build and move over just your customisations that are still required (rather than any bug fixes for old versions or functionality that is replaced with v9.1). Of course that sounds like the costly option but decommission the old hardware/virtual environments and you end up with an ITSM environment fit for the future, in support and able to cope with the requirements of ITSM v9.x. A clean v9.x install will generally be faster, easier to support and of course easier to upgrade to the next ITSM version. You will of course still need to review the customizations you have applied to your current system and decide what you need to retain, but that is of course best practice with an upgrade anyway. While ITSM 9.1 data wizard is vastly superior to older versions and far more capable of managing the data in your production environment, what it will not do is handle the data migration from your old version. You will want to migrate over the foundation data, and the transactional data onto ITSM 9.x . This is an ideal time to clean up data, remapping Prod cats and Op Cats etc. and potentially archive some of the tickets that you no longer need direct access to. We use our Customer Move Tool (more info http://www.alderstone.com/cmt) for the migration from previous ITSM versions to the latest, as we can migrate all modules data or a reduced set (including extracting single companies and migrating just their data), depending on your requirements. In general we've been able to move all data within one day and the upgrade process becomes very smooth indeed. Please let me know if you would like to talk about this in more detail or I can set up a Demo of our migration tool to show you the flexibility and power of the application. In the mean time if you have specific questions around upgrades, please let me know. regards Sean *Sean Harries* Alderstone Consulting Ltd Revolutionise your management of BMC Remedy ITSM Services with CMT <http://alderstone.com/cmt/> Mobile: +44 (0)7976 558048 Skype: seanharries MSN: seanharr...@alderstone.com <sean.harr...@alderstone.com> e-mail: sean.harr...@alderstone.com Linkedin: http://www.linkedin.com/in/seanharries On 21 January 2016 at 03:19, Su Kaur <remedyiss...@gmail.com> wrote: > ** > We are also planning to do an upgrade from 7.6.04 to 9.0.01. Ours is a > highly customized system. All the development is in base development mode, > no overlays and none of the ITSM modules being used. > We have a separate app and mid tier server using SQL Server. > Since the configuration of current prod is not good and its all messed up, > we are thinking of setting up a new 9.x server. > What would be our best bet? Copy data and then upgrade? Would this move > all the customizations? > > Thanks! > Kaur > > > On Wed, Jan 20, 2016 at 3:14 PM, Daniel Wu <danie...@cox.net> wrote: > >> ** Thanks Warren. I was posting a question on your chain at the same >> time. I appreciate the link you sent. I'd be sure to check it out. You can >> answer my question here in my posting chain, if you like. >> >> In our particular environment, I will have to stance up another instance >> and run in parallel to compare, then do the cut over. And that won't be the >> live system. >> >> >> On Wednesday, January 20, 2016, Warren R. Baltimore II < >> warrenbaltim...@gmail.com> wrote: >> >>> ** >>> Daniel, >>> >>> We just completed the upgrade from 7.6.04 to 9.0.01. For the most part >>> it was relatively easy albeit a VERY long process. I strongly urget that >>> you take a look at this link if you haven't. We followed this process and >>> found it to work quite well. >>> https://docs.bmc.com/docs/display/public/brid90/Upgrading+from+a+version+7.6.04+or+8.0.xx >>> . >>> >>> Some things to keep in mind. When you are working on the >>> Reconciliation, you must have a copy of your current installation running >>> on a network that your development server can see. This is necessary so >>> that the developers studio can connect with both for the "compare and >>> contrast" part of the show. This part can take awhile depending on the >>> number of customizations you have made. Don't make the mistake that I made >>> and not take the time to really look at them. I ended up losing some >>> things that I really needed >>> >>> The problems we have run into since Monday when we went live are these: >>> >>>- Reports can no longer be unlimited. Even though the flags are set >>>for the 3 properties in config.properties on the mid tier servers are set >>>to 0, they seem
Re: How to migrate any Service Now project to Remedy?
Hi Abhi, We have been asked this question more and more in the last 6 months as people's requirements and business challenges change. Using legacy tools it is possible but very time consuming to manually move raw ServiceNow data to ITSM The greatest challenge around this type of migration is understanding all the underlying data structures that hold ITSM together to ensure your data will work correctly in ITSM modules after it has been migrated from ServiceNow. While it is straightforward to drop some ServiceNow tables onto an ITSM system for reference, taking a ServiceNow incident with all its related data and migrating it to be a working ITSM Incident ticket is more challenging. We originally designed our Data Migration Tool ( http://www.alderstone.com/cmt.html) to migrate from ITSM to ITSM but we have recently been working hard to bring out CMT v1.3 this will migrate data between ServiceNow and ITSM. We anticipate that v1.3 of CMT will be fully available very soon, but is already in use by our consultants and we would be happy to talk to you about the tool and around your migration of data from ServiceNow to ITSM. Note on Premise or SaaS is not an issue here, the CMT software will migrate from On Premise to Cloud, Cloud to Cloud or Cloud to On Premise so I'd like to think we have you covered on your migration here. Please contact me if you have any questions or want to know more thanks Sean *Sean Harries* Alderstone Consulting Ltd Revolutionise your management of BMC Remedy ITSM Services with CMT <http://alderstone.com/cmt> Mobile: +44 (0)7976 558048 Skype: seanharries MSN: seanharr...@alderstone.com <sean.harr...@alderstone.com> e-mail: sean.harr...@alderstone.com Linkedin: http://www.linkedin.com/in/seanharries On 12 January 2016 at 17:48, Abhi$hek <abhi.masc...@gmail.com> wrote: > ** > > Yes SNOW is on premise and migration will be from SNOW to Remedy ITSM > > Cheers, > Abhi > On 12 Jan 2016 22:57, "Joe D'Souza" <jdso...@shyle.net> wrote: > >> Is SNOW on premise? >> >> Cheers >> >> Joe >> >> >> -Original Message- >> From: Action Request System discussion list(ARSList) >> [mailto:arslist@ARSLIST.ORG] On Behalf Of Stan Feinstein >> Sent: Tuesday, January 12, 2016 10:22 AM >> To: arslist@ARSLIST.ORG >> Subject: Re: How to migrate any Service Now project to Remedy? >> >> Abhi, >> >> Is your client using Service Now's project management functionality? If >> so, >> please call me at 310-230-1722. Project Remedies' ActionProgram Manager >> Plus is Remedy-based and better / richer than Service Now's capabilities >> in >> this area. >> >> Stan >> w. 310-230-1722. >> c. 310-428-5748. >> >> -Original Message- >> From: Action Request System discussion list(ARSList) >> [mailto:arslist@ARSLIST.ORG] On Behalf Of Abhishek Anand >> Sent: Tuesday, January 12, 2016 6:58 AM >> To: arslist@ARSLIST.ORG >> Subject: How to migrate any Service Now project to Remedy? >> >> Hi Team, >> >> >> >> We are having the requirement for migration of the Service Now project to >> Remedy. >> >> Anyone having any high level view on the same. >> >> >> >> Early response will be highly appreciated. >> >> >> >> Cheers, >> >> Abhi. >> >> >> >> ___ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the >> Answers >> Are, and have been for 20 years" >> >> >> >> ___ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> "Where the Answers Are, and have been for 20 years" >> >> >> ___ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> "Where the Answers Are, and have been for 20 years" >> > _ARSlist: "Where the Answers Are" and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
Re: Regarding MS SQL Server to Oracle Migration
Hi Radhika, Thanks for the question, the Alderstone CMT does indeed migrate from non-unicode SQL Server to unicode SQL Server, with no issues. I agree with other arslist posts, don't let the DB Migration convert to Unicode, there are generally issues and you are of course right, 400Gb through the Java API would be very slow. I would suggest you use our Customer Move Tool (more info http://www.alderstone.com/cmt) for the migration from previous ITSM versions to the latest, regardless of database version or non-unicode. We can migrate all modules and data, or a reduced set (including extracting single companies and migrating just their data), depending on your requirements. In general, we've been able to move all data within one day and the upgrade process becomes very smooth indeed. Please let me know if you would like to talk about this in more detail or I can set up a Demo of our migration tool to show you the flexibility and power of the application. In the mean time, if you have specific questions around upgrades, please let me know. regards Sean *Sean Harries* Alderstone Consulting Ltd Revolutionise your management of BMC Remedy ITSM Services with CMT <http://alderstone.com/cmt/> Mobile: +44 (0)7976 558048 Skype: seanharries MSN: seanharr...@alderstone.com <sean.harr...@alderstone.com> e-mail: sean.harr...@alderstone.com Linkedin: http://www.linkedin.com/in/seanharries On 7 March 2018 at 13:13, Narayanan, Radhika <radhika.naraya...@cgi.com> wrote: > Hi, > > > > Is Alderstone CMT DB Migration solution also capable of migrating data > from non-unicode SQL Server to Unicode SQL Server ? > > > > Previous arlist posts recommend not to carry out DB migration to convert > non-unicode to Unicode, instead install AR fresh with unicode and then use > Java API to migrate data. However, to migrate ~400 GB data through Java API > will need many months of time ! > > > > *Thanks,* > > *Radhika Narayanan* > > > > *From:* ARSList [mailto:arslist-boun...@arslist.org] *On Behalf Of *Mohamed > Kamruzzaman > *Sent:* Monday, March 05, 2018 10:35 PM > *To:* ARSList > *Subject:* Re: Regarding MS SQL Server to Oracle Migration > > > > Hi Vinod, > > > > Hope you are well. This is a scenario we have helped many customers with. > As Gavin mentioned the Alderstone CMT solution can migrate data from MSSQL > to Oracle at the database level maintaining all relationships and data > integrity as well as doing all necessary conversation for the database > particulars. > > > > We had one customer who spent 12 months trying to develop and model the > Remedy data model, after which they reached out to us and we were able to > migrate from SQL to Oracle in a couple of months. > > > > Let me know if this is of interest. Feel free to reach out. > > > > Thanks > > Mohamed > > > > —— > Mohamed Kamruzzaman > Alderstone Consulting > > Personal Meeting Room > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.gotomeet.me_MohamedK=DwMFaQ=H50I6Bh8SW87d_bXfZP_8g=blQKSsGpUV3vEddB0ufOi2izy5lUOikNQGO3le4xQkw=bMlqLRT9Ee7IhpV1CE6-bdQC_HNR1Hwu3qPs53-YlVA=PJgHhISHBNp0-B23zPGhrUJyfqOlAe0g_nFGqrVRkBg=> > > mobile: +1 650 308 4633 <(650)%20308-4633> > skype: mkamruzzaman > email: mohamed.kamruzza...@alderstone.com > > Revolutionise your management of BMC Remedy ITSM Services with CMT > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.alderstone.com_cmt.html=DwMFaQ=H50I6Bh8SW87d_bXfZP_8g=blQKSsGpUV3vEddB0ufOi2izy5lUOikNQGO3le4xQkw=bMlqLRT9Ee7IhpV1CE6-bdQC_HNR1Hwu3qPs53-YlVA=K4usLoBN_RbCj7v40ou9gr_ASjRrs6s49nwFNEpyDL8=> > > > > On 5 Mar 2018, at 6:03 PM, Gavin Coleman <gcoleman.arsl...@gmail.com> > wrote: > > > > Have you looked at Alderstone's CMT product? I've used this before and can > recommend it. It's blindingly fast and can perform data transformation as > well. > > > > https://www.alderstone.com > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.alderstone.com_=DwMFaQ=H50I6Bh8SW87d_bXfZP_8g=blQKSsGpUV3vEddB0ufOi2izy5lUOikNQGO3le4xQkw=bMlqLRT9Ee7IhpV1CE6-bdQC_HNR1Hwu3qPs53-YlVA=QatyqJWmQcX1B2mhKGTC7l5f03P6jS3ENSXUouMR6kk=> > > > > > > > > On 5 Mar 2018 4:55 pm, "Vinod Gaidhani" <vinod.gaidh...@gmail.com> wrote: > > Hi Team, > > > > We are planning to migrate from Microsoft to Linux [8.1 to 9.1] and as > part of this, we will have to move to Oracle as well. Can anyone please > share approach/experience of doing this at Database level using DBA > utilities. Or there is no otherways but do it at API level only because of > the way data handled in both databases [for LOBs/etc] > > > > We have explor
