Moving to NXT. What do you wish you had done beforehand?

Options

Hi! We are one of the few orgs left who are self-hosted on old school RE7. We are starting the discussion of moving to NXT finally, and I'd love to hear your ideas and thoughts. What do you wish you had known or done before you moved over? Where would you focus on clean up if you were in my shoes? Any hints, tips or ticks?

Thanks!

PS I should have mentioned that I am pretty familiar with web view and NXT myself, having used it for several years, taken all the classes, and getting certified when I was working at Omatic. A few others of my staff have used it as well. I'm just more concerned about nitty gritty clean up to make things nice and clean from the start. But I am loving all the tips so keep 'em coming!!!!! Thanks!

Comments

  • Austen Brown
    Austen Brown ✭✭✭✭✭
    Ninth Anniversary Facilitator 4 Name Dropper Photogenic

    @Amy Barker - The first change you'll need to think through is going from self-hosted to Blackbaud hosted. In the last 1.5 years hosted customers have lost some features due to security concerns - primarily the Microsoft Integration and the ability to create/edit Crystal Reports within the database. On the surface level, the Microsoft integration doesn't seem so bad, but when you really start thinking about it the headaches arrive - here's a resource that will help you think through the changes and how this may impact your current processes.

    Once you make it to hosted, NXT is less of a ‘migration’ and more of a ‘flip a switch’ to turn on another view. When that step arrives, here's a KB Article of things to check:

    Echoing @Dariel Dixon learn what you can about Web View now - it is our future. Do what you can to stay up-to-date with new releases to WV; they happen weekly (check out the Announcement section of the forum for more info). Blackbaud is actively developing WV and has started recreating features from DBV - once released to WV, they will then turn off the feature in DBV; first up, is table codes (Configuration > Tables). I recommend reading through this blog -

    https://community.blackbaud.com/blogs/13/9202

    As @Joe Moretti mentioned there is a terminology change - check out this KB Article for a breakdown of the new lingo you get to learn! Additionally, there are areas that exist in WV but not DBV and vise versa - I'm hopeful that in the future we will exist in a fully functioning one view world.


  • @Amy Barker If you'd like a preview of what it looks like, I'm sure I can get my boss to agree to me showing you around Mickey Mouse's record in my database. Just let me know.

  • @Amy Barker Also, not all fields that are viewable and may have been made required in db view are viewable in web view. If they are not viewable in web view, they are not required in web view and records can be added without filling out these fields. Since it's a sore topic for my organization, Region on addresses is one of these fields that immediately springs to my mind. So, my suggestion is to be aware of which fields in your db are required and used for reporting/querying and how they translate in web view, and, also, whether as a result you may want to set a policy of certain information to be added only through db view (which is what we did for addresses in my org.)


  • @Amy Barker If you're still using the link between Microsoft and RE (since you're self-hosted), definitely take some time to consider all that you will need to revise in your processes (particularly with Acknowledgement Letters and other Mail functions).

  • @Amy Barker I did this with my previous organization. I would suggest taking the NXT classes ahead of time while you are transitioning. NXT is much easier to use than database view so there is less of a learning curve. The classes were a huge help – especially learning how to use lists and importing them from database view. You will find this is a life-changer!! Good luck and have patience. Don't be afraid to retake a class too once you start using.

  • @Amy Barker At my previous office we didn't give anyone else an invitation to it until we had worked with it for a few weeks ourselves. Two of us learned how it all worked before giving the less technical people in our office access. We looked at their work centers and that showed us things that we needed to clean up before having them use it. We ended a lot of old solcitor assignments and proposals. That was in 2015 before dashboards and insights existed. My advice for those is to start small - and take the classes about them. Make insights that match queries and reports in database view to make sure that you're capturing the correct information. The dashboards and insights work really well, but you need to learn how they work. You also mught have to rethink some of the ways you are currently entering data. That's ok - we've all creatively entered data into the database view that might not translate as well in web view. That isn't necessarily a defect in the web view - it's just something that you may need to reconsider.

  • @Heather MacKenzie thank you! I'm really familiar with web view myself and have my certification from when I worked at Omatic. I was lucky to be able to work in it a lot. I know a lot has changed in the past almost 2 years. But thank you for your offer!!!

  • @Lee Grisham:

    Oh, and Business Rules set in DB view DO NOT apply in NXT. ?

    I did not know this! Have you found ways to work around it?

  • @Joe Moretti Spot on - so very well put! I'm going to quote you, Joe!

  • @Tatyana Leifman:

    @Amy Barker Also, not all fields that are viewable and may have been made required in db view are viewable in web view. If they are not viewable in web view, they are not required in web view and records can be added without filling out these fields. Since it's a sore topic for my organization, Region on addresses is one of these fields that immediately springs to my mind. So, my suggestion is to be aware of which fields in your db are required and used for reporting/querying and how they translate in web view, and, also, whether as a result you may want to set a policy of certain information to be added only through db view (which is what we did for addresses in my org.)


    Related to this one, our county field in DB view uses a table that regular users cannot edit but web view completely disregards this and 1. it doesn't use the table at all and 2. users can just type whatever into that field, which then adds it on to the end of the table if it is not an existing entry.

    To deal with this, we do tell our colleagues to add new addresses in DB view (so they can also use SmartZip) but in addition every so often we take a look at what new active entries got added to the end of the table and fix whatever needs fixing.

Categories