After getting back from work yesterday evening and having dinner she set to work on our site and had it running in half an hour. This evening the new updates must come first, then the faults in the messaging.

If I didn't  tell you before, her name is Pinky.

Having counted up the number of pages we have on the site, it would take far too long and cost far too much to change over from Drupal to a different software. SInce everywhere has its advantages and disadvantages, we are better sticking her and working with an excellent web director to sort out the problems. I am sure that you will bear with us.
Completed Stratton/Wheldon regime for aggressive secondary progressive MS in June 2007, after four years, three of which intermittent.   Still improving bit by bit and no relapses since finishing treatment.

When considering converting, it's not the number of pages that matter, but rather the complexity of the site. Importing all the posts into another system is something that would be done by a program, and having a bigger site just means that the program runs for (say) five minutes rather than one minute. For instance here's a Drupal import script for Discourse:…

That's 200-some lines of Ruby code that connects directly to Drupal's database, slurps up all the posts, and imports them. It also saves the old forum structure (the categories) and puts each post in the correct category. But it doesn't make any effort to have the old URLs work; and even with all the old content saved, having it all at different URLs is a major downside. Any links from other websites into Cpnhelp would be broken, as would links that people have put into their own posts here. All the links at the top of the page, for instance to the page for patient stories, would have to be redone. And that's just the most obvious thing that would be lost; I'm sure that there are others too. In general, the more customized a site, the harder it is to convert, and this one seems like it's been customized a fair bit.