Possible Disadvantages of Google Apps

• * If you want to back up individual email boxes, you will need to obtain a separate solution to do this or work with the IMAP/POP access to download your messages locally.
• * You do not have any administration over individual messages or mailboxes outside of changing passwords. You cannot delegate access to another account or a group of accounts. For some people, this is really important. The most Google Apps lets you do is change a user’s password or tell people to share passwords. I’ve seen hints that there may be a little more functionality in the Enterprise edition, but have not personally tested that.
• * Setting up a shared calendar for everyone in the domain takes a little bit of work, though it’s gotten easier in the recent months. Setting up resources such as rooms is quite a bit more difficult than doing the same in Exchange.
• * You are at Google’s mercy for backups and restores. If you host your own email or use a dedicated email host, you may have more granular backups.  On the flip side, if you host your own email, you’re responsible for the backups so this may even out for some people.
• * Our biggest limitation – trying to send out to a large number of email addresses for bulk mailings. Google has an upper limit of 100 distinct email addresses at a time and 500 distinct email addresses per day per account.  That means that if you want to send out an email to a larger congregation, you’ll be better off with using a dedicated email service or some other notification method.  Google Apps will definitely run into some limitations.  You’ll know that the emails failed because they’ll all come back with a “failed permanently” message.
• * In order to enable each user’s POP or IMAP access or to set auto-replies or forwards, you need to log in to each account. I wanted to be sure that people were set up with IMAP access and that certain accounts had an auto-response on every email. Having to log in to each account to set this bothered me a little from an administration standpoint. Using multiple browsers helps some, but it still takes some extra time. I hope the administration side grows as Google Apps gets more popular.

For our purposes, the administration is a little awkward, but we have a small number of users. The limitations on how many emails we can send per day affects us only when we’re doing a new program or holding a new event. Other than that, the benefits far outweigh the negatives. With all of that being said, I wanted to concentrate on the next areas of concern in our migration process.

3. Migration process to Google Apps.

  For most people, this is one of the big concerns. Your users probably have a lot of emails already stored either in Exchange or in POP3 and local stores.  If your email client supports IMAP, you could simply add your Google Apps account as a new IMAP account and then drag and drop your emails from your old folders into Gmail.  If this option won’t work, there is a Google Email Uploader that may work for you. You can find the instructions here or the FAQ here. Note that this tool is designed primarily for Google Apps email and will probably not work with a normal Gmail account.

  For our purposes, we started forwarding a copy of each user’s mail as it arrived on our old web host accounts.  That let us pick up from that point and not worry about migrating those emails. It was also easier for us than logging into each account and setting up POP access to the old servers. The older email still lives in Outlook PST files for the moment, mostly because our users haven’t asked to have them migrated yet. We definitely plan to migrate them, but nobody has even mentioned missing old emails so far.  That probably says something about our use of email, but I’d rather not concentrate on that right now.

  What will work best for you depends quite a bit on how heavily each person uses email. Some may be a simple drag and drop through IMAP. Some may want to organize everything in specific categories. Do some planning with your users and you will have a much better success rate.

4. Current usage of Google Apps

  We made it easy for our staff to use by setting up some basic aliases for our domains. Google provides some suggestions for you if you want to change their default (long) URLs to something friendlier. For example, if you use Calendar, the first option you see when you choose to change the URL is calendar.yourdomain.org.  You may customize this as you see fit, but I’d recommend coming up with something easy to remember and setting up your CNAME aliases shortly afterwards.  Google makes this pretty easy by including instructions for all sorts of DNS hosts. Just follow those to add new CNAME aliases and you’ll be able to point your users to much easier to remember addresses.

  Our primary use of Google Apps is still email. We don’t do too much planning at this time, though I’m trying to encourage at least a small internal calendar for our staff and workers.  We still set up some IMAP clients for sending more richly formatted HTML messages, especially when doing announcement mailings. Because we regularly send out messages to groups of people, we have created several different Groups within the domain management piece. This lets our church administrator define a group such as “Men” or “Women” that he can use to send announcements to a targeted set of people. Google Apps allows some control there so members may email that group, only specified people may email the group, or the group is accessible to everyone.  Most of our email lists of this sort are limited to certain owners to avoid possible abuse of the address tied to the group.  Other listserv systems may be better suited to this purpose so I’d still advise looking around at your options before choosing to set up groups on Google Apps.

  Having finished the basic configuration of Google Apps, I’ve mostly had the experience now of being able to sit back and let it run.  The worst problem we had was when our users tried to set up or access their accounts on new machines. The default CAPTCHA images are pretty hard to read even for someone used to CAPTCHAs. For older users, the images are pretty hard to figure out and I’ve had to talk people through this a couple of times. However, once everyone is up and running, I don’t hear anything about email issues. In fact, most of the users like the ability to log in easily while not in the office.

5. Other benefits of Google Apps for the small church

  So what other benefits are there to Google Apps? For our church, we’re content with just email. However, I know of churches who use the Calendar and Docs areas heavily to share important internal documents. Some set up Sites within their domain for internal use and share information through those sites.  However, the biggest benefits after email are
likely to be found in the Calendar and Docs areas.

  With just a little effort, your users can set up a new calendar to plan out an event or to track vacations. They can then share that calendar easily to people within the domain so others can either see the details as they arise or even help edit the calendar events. This is a great way to ensure that your event planning runs smoothly. It can also be helpful to keep track of your staff members’ appointments and allow your office workers to help them plan out their schedules. if you want, you can even set up a public-facing Event calendar that can be pushed outside of your Google Apps users.  People can subscribe to the calendar through a URL or through RSS feeds. If you have a calendar of events that changes regularly, this may be very helpful for you.

  I’ll touch on Google Docs briefly. Google Docs includes Word Processor, Spreadsheet, and Presentation modules as well as a PDF (Adobe Acrobat) viewer. Any PDF files can be viewed straight out of your Google Apps email now and then saved if you wish into your Documents.  Most common Office document formats (Word, Powerpoint, Excel) can be viewed or imported into Google Docs, though you may lose formatting along the way so the document may not appear exactly the same.  If you just need to work on a basic Word Processor, Spreadsheet, or Presentation, Google Docs can get the job done. It’s a great way to take notes and then share them easily to your users or to save an initial draft for later work when you’re not near your normal PC.

If you want to keep up with the changes to Google Apps, be sure to follow this RSS Feed. It’s a great way of getting notifications about everything that Google is rolling out to your users.

I’d love to hear from you now. What are you doing? What questions did I not answer? How do you use Google Apps for your organization?

For Him,

-Peter Schott

1. Where we were

Prior to our migration to Google Apps, we depended on the e-mail solution provided by our hosting provider. While it worked well for a lot of things, we felt that our ability to manage and work with our e-mail was not very efficient. Our church was considering changing our hosting provider to a new company that would work better with our website CMS and provide a little more storage so we would not keep bumping up against space limits.  However, that left us with the problem of how to proceed with our e-mail as all accounts, mailing lists, and management were handled by our hosting provider.  At this point, we began to explore our options – setting up personal e-mail accounts, setting up e-mail with our new host, or hosting with a 3rd party.  Having read some information about Google Apps for domains, we decided to explore that as a possible solution.

2. Exploration of Google Apps – benefits, drawbacks, extras

Obviously one of the major concerns with using a solution is whether it will meet your needs sufficiently. Our needs:

1. E-mail hosting

2. Easy Web Access for e-mail

3. Integration with existing e-mail tools, Outlook in our case.

4. A small learning curve.

5. A calendar for internal schedule coordination.

Google Apps offers 3 different editions – a Free edition, Business/Enterprise edition, and a Non-Profit edition that is essentially the same as Enterprise, but only available to non-profits. We started at the Welcome site to get more information. Looking into the messaging offerings (e-mail and IM), we found that we would get 7 GB of storage per user, 25 for non-profits/enterprise and would meet Requirements 1-3 above.  From my prior experience with G-mail, I realized that there would be a small learning curve for our users, but nothing insurmountable.  Requirement #5 is met through Google’s Calendar solution and details can be found here.

Of course, there’s more to Google Apps for Domains than just e-mail and calendar apps.  They also include Word Processor, Spreadsheet, and Presentation software, and basic web page editors mostly intended for internal use called Google Sites,

Testing It All Out

Of course, I wanted to test this out before actually migrating our church to it; therefore, I signed up for a personal domain for myself and began the sign-up process for Google Apps.  This used to be an easy process for “Standard” users because Google offered one button for Free and one for Premier.  The Standard edition link is now much smaller.  Both signup links can be found here. However, if you’re trying out Google Apps for yourself before making any recommendations, you can get started for your personal domain here. This will take you to the “Standard” edition page to sign up.

At this point, you will have an option to buy a domain name or enter one you already administer. I had already purchased a domain name so used that. You’ll need to provide some basic information, including the name of your organization and other information necessary to work with the domain. Choose your administrator account name carefully as you can’t change this once your account is set up. I probably would have chosen differently had I known this ahead of time.

In order to start using Google Apps, you need to prove that you own your domain. You can do this by uploading a special file to your web site or by creating a CNAME DNS record to create an alias that points to Google. Either way, Google will be able to verify that you own the domain pretty quickly after that and you can start customizing your configuration.

I quickly added CNAME aliases for the various services Google provides, mostly using defaults buy customizing some where I thought it made more sense for my use.  For example, docs.mysite.org is aliases to ghs.google.com and will direct anyone using that DNS name to the Google Docs area of my Google Apps. Google provides very clear instructions for different DNS Management tools to help you out. I was quickly able to migrate most of my settings over to Google Apps, including e-mail for my domain (which was new to me so I didn’t have any down time to worry about).

After some testing with my account, I was ready to make a plan for our church to migrate from our hosted POP E-mail solution over to Google Apps. I’ll provide more details for that in my next post.

Coming soon…

3. Migration process to Google Apps, (focus on e-mail)

4. Current usage of Google Apps

5. Other benefits of Google Apps for the small church

I am responding to Garrett’s comment on Webmedley because I think it’s terribly short sighted and biased. First off, I do need to acknowledge that Webmedley is a sponsor of this site and that could tend to make me biased but I don’t partner with any person or organization that I can’t fully endorse and believe in. With that said, let’s consider this product objectively.

Garrett says:

Honestly I think this is a terribly overpriced CMS especially for small churches. $1000 a year? Really?

First off, the platinum package does cost $999.95 per year, which gives you everything and then some. But the gold package is $499.95 and it gives you everything except blogs, chat room, directory, store and forums. The silver package is $199.95 annually and gives you less features, obviously, but still enough to get a good site started. So, Garrett, if $1000 per year is “…terribly overpriced…” for you, don’t miss the smaller packages. This type of CMS is ideal “…especially for small churches…” because it will cost so much more for someone being paid to design a site with similar functionality, even using any other CMS already out there.

Define easy

Garrett also recommends that churches “…try something easier first.” Here’s a breakdown of his suggestions:

• Get a blog and a google calendar
• start looking at ALL the products out there
• Sky by ElementFusion
• ExpressionEngine
• wordpress
• Textpattern
• Go to Godbit.com – find out what others are doing.
• There are plenty of resources out there that will do a lot more.

Clearly, Webmedley’s target audience is not Garrett because Garrett seems fairly geeky and knowledgeable in technical things. But Garrett, check this out, did you know that out of 350,000 churches in the U.S., 85% of them average less than 200 in weekly attendance? Did you know that the actual average attendance in U.S. churches is 87? Worldwide, I’m sure that number averages even less. Nearly 300,000 churches in the U.S. see less than 200 people per week and the fact is, people like Garrett and I are not in most of those churches.

Pastor does not equal web designer

In most churches, the pastor is the one making the decision to have a website or not, and most pastors have little knowledge about blogs and Google calendar, let alone Sky, ExpressionEngine, WordPress, TextPattern or GodBit. Plus, GodBit is not designed to reach the non-technical person, no matter how hard they try. It’s a great community for the web designer and the web designer wannabe, but trust me, the average pastor is not a web designer and if anything, they are far from it.

We are all web designers, right? Anyone can create a website in a short amount of time, seriously. But how many church websites suck? Too many, in my opinion. Generally, a church is not going to find someone within the church, with a level of talent to design a site correctly and volunteer their time and effort.

True cost

So, Garrett, I get where you’re coming from, I understand there are many other options out there and I know for you, it’s silly to even consider Webmedley, but you are not their audience. They are aiming for the majority of churches out there that do not have a website yet or even a church with a site already that wants to take it up a notch, with little effort. A church will pay far more than the cost of Webmedley for a professionally designed site and end up with less functionality than what Webmedley brings to the table.

Extending you reach

Webmedley is great if you are in the average church (i.e. small) and it’s also great if you are in a larger church. It is an easy way for your church to have an excellently designed and fully functional website.

If your church wants to extend it’s reach to your community via the web, I would again encourage you to visit Webmedley and check out what they have to offer and compare that to the cost of having it done well by somebody else.

Thanks for your comment, Garrett! I needed to clarify the value and purpose of Webmedley better than I did initially.

Whatever you do, work heartily, as for the Lord and not for men, 24 knowing that from the Lord you will receive the inheritance as your reward. You are serving the Lord Christ. Colossians 3:23-24 (ESV)