Myth:  Migrating to Office 2007 is like every other software upgrade or switchover.
Reality: The application looks radically different and is a complete overhaul of the user interface. There are no menus and no toolbars. Many information workers won’t even be able to open files without training and assistance. In past upgrades, an information worker’s knowledge of how to get to the features in the previous version was 95 percent effective in the new version. For Office 2007, it is zero percent effective.    

 Myth: Information workers will benefit from Windows 7 without training and support
Reality: A learning curve is guaranteed when information workers, or even an internal help desk staff, are faced with tools, applications or operating systems that look differently. A lack of proper training and support will prolong the adoption period. Maximizing the productivity increase — and resultant ROI — from the new tools in Windows 7 requires training in the theory and support in the practice of using the new tool. Read more myths and realities of an Office 2007 and Windows 7 migration and eight service levels needed to prove migration ROI http://www.pchelps.com/html/o2007mythsrealitiesroi.asp

There’s no need to wait in line at the local Blockbuster; you can watch Netflix on demand. You can order your groceries online and have them delivered, print a boarding pass at the airport kiosk (no humans necessary!), and have your dry-cleaning delivered with just a click. Even GPS systems, which were once a luxury in cars, are becoming a standard. Have we lost our sense of direction? No, we like having a faster, more convenient way of getting there.

The workplace is no different. Chances are your office cafeteria has swipe cards, self-service, and grab-and-go options. If you’re in sales or marketing, your company may have invested in a pricey CRM solution to boost your productivity. If you’re in accounting, or any department really, it’s the same: get more done in less time.

“Whichever solution he chooses, he’s right where he started – lost in a sea of #REF!s.”

Time is money, indeed. It’s an old saying, but in the current financial climate, stakeholders, company owners and managers really mean it. So, why then, when it comes to delivering convenient, efficient support for desktop and mobile device applications is it not a priority for IT leaders?

Consider the following example: Employee X just switched positions within a company, and he is now responsible for his division’s quarterly sales reports. When he tries to update the existing spreadsheet with current figures, his formulas return errors. He’s stuck, and he has no idea how to begin to troubleshoot.

He can ask a colleague to help, which will waste the time of two employees. He can scan Excel’s often-useless help menu. Or he can call a help desk tech who spends all day resetting passwords and rebooting servers.

Whichever solution he chooses, he’s right where he started – lost in a sea of #REF!s, and far from a solution that is efficient and convenient. And not only is he stymied, his company is losing money on his diminished productivity.

If he had access to on-demand, expert support for his desktop applications, the same applications he and the rest of his colleagues rely on every day to stay productive, this dilemma would be a minor interruption, with minimal impact on his productivity. (Stephanie Maurer)

FIND MORE INFO IN: Small Business | BlackBerry + Mobile Devices | Office 2007 Migration | PC Helps eTraining | Desktop Application Support | Contact PC Helps

Myth No. 1: You can make Office 2007 look and act like Office 2003.

“Two words: no menus. Two more: no toolbars.”

Scads of third-party applications have cropped up that promise to make Office 2007 look and act like 2003. Some are effective; most miss the point. Holding on to the old interface will only serve to diminish your Office 2007 migration return on investment.

Myth No. 2: Migration support needs disappear completely after a few weeks.

No, no, no. Microsoft designed the new interface to make it easier for users to find features that were available in older versions, but were buried in an elaborate menu structure. It’s working, too. Months into a rollout, your employees will be finding tools they never knew existed – and they will need help learning how to use them. To expect IT generalists to know how to use long-hidden features is downright unreasonable.

Myth No. 3: Migrating to Office 2007 is like every other migration.

Two words: no menus. Two more: no toolbars.

Many users will not even be able to open files without training and help. Office 2007 is a complete overhaul of the user interface. In previous upgrades, knowledge of how to get to features in the previous version got users where they wanted to go 95 percent of the time. With 2007, it’s zero percent.

Myth No. 4: Handling a migration without outside help will give my staff a chance to shine.

Don’t turn your IT staff into scapegoats. The scale of end-user need when Office 2007 hits a desktop guarantees your IT department will be overwhelmed.

Myth No. 5: I have smart employees. They’ll have no problem figuring out how to use Office 2007 on their own.

An employee does not call the general help desk when he can get the answer from a colleague who sits near him. If none of his colleagues know how to use Office 2007, and he calls a generalist at the help desk, how much expertise will he find there?

FIND MORE INFO IN: Office 2007 Migration Checklist + Tools | Migration Case Study | PC Helps eTraining |Desktop Application Support | Contact PC Helps

Lesson 1: Icebergs and Undergrounds

In the common view of desktop application support, calls typically account for less than 5 percent of help desk volume. Very often, the percentage is even less than 1 percent. The visible portion of the “iceberg” is quite small.

But, like an iceberg, what you see on the surface (that is, what most CIOs see when reviewing help desk metrics) is merely a fraction of what truly exists. The reality is that the demand is there; it’s just being absorbed by the organization in other forms:

• Peer support (Joe asks Mary for help)
• Abandoned support (Joe gets stuck and walks away from the task altogether)
• Rework (Joe can’t figure out how to make the software do what he needs so he re-tools his work to get around the problem)
• Self-help (Joe wastes time consulting the software help feature, scouring the Internet for help, reviewing manuals, etc.)

The productivity impact of these “underground” support channels averages three hours per solution at a cost of $48 to $196 per solution (depending on salary). And this doesn’t even account for the additional cost of the peer’s time (e.g., Mary in the example above). In comparison, the average solution with a best-of-breeds software application support provider is less than $25.
The true level of demand typically ranges from 5 percent to 15 percent of all help desk call volume, assuming all troubled end-users are reaching out to the help desk instead of consulting their underground channels. When a company is migrating to a new software suite or version, or rolling out additional mobile devices, the surge in demand for support can reach 40 percent or more of help desk volume.

Lesson 2: Contrasting Models

There is a significant contrast between supporting desktop applications under the standard help desk model versus employing a best-of-breeds approach for “how-to” support.
The standard help desk model employs a tiered support structure where only a relatively small percentage of issues (around 20 percent) are resolved on the first call, another roughly 35 percent require a few days to turn around, and the remaining 45 percent either take longer than a few days, or sometimes never find resolution.
This model staffs agents for things like break/fix, network connectivity issues, and hardware and software installs. They are, by design, generalists that have little knowledge on desktop applications and mobile devices (“jack of all trades, master of none,” to borrow a phrase). Additionally, the typical help desk is built on the premise of “lean staffing,” meaning nominal off-hours coverage, fewer bodies than required to meet peak calling periods, and frequent “leave a message” instances for troubled end-users.

In sharp contrast, a best-of-breeds sourcing partner does not employ a tiered support structure, leading to 90 percent or more of issues being resolved on the first call, and virtually no issue outstanding beyond 24 hours (excluding certain time-intensive development projects). Unlike the typical help desk model, a best-of-breeds sourcing partner employs certified software specialists on the front lines that focus exclusive attention, day in and day out, on desktop application and mobile device support. In this model, response time is critical, listening to music in queue is offensive, and leaving a voicemail is completely unacceptable.

Additional contrast stems from that exclusive focus. A best-of-breeds sourcing partner solves the real problem, not merely the symptoms described by the end-user, in addition to identifying related topics, delivering multiple solutions on the same call, and recommending future courses of action for training. The specialist, by virtue of experience and expertise, can solve today’s issue and reduce tomorrow’s need for similar support. That translates into dramatically enhanced ROI for an organization’s investment in software and mobile devices.

Lesson 3: Apples & Oranges, and How Much They Really Cost

The typical perception of specialized desktop application support is that it is expensive compared to average help desk metrics. The reasoning follows a general pattern: Our average call lasts X minutes and costs Y dollars. The average call to a niche, “how-to” support provider is expensive when compared to our internal cost per call for help desk assistance.
But that’s comparing apples to oranges.

For starters, comparing “costs per call” completely misses the key distinction between a “call” and a “solution.” While a typical help desk call may focus on an isolated, solitary issue and the associated solution such as “connecting to the web,” desktop application support generally requires the delivery of multiple solutions on a single call.

A customer calling in about Excel, for example, may need help fixing a formula, formatting cells, and modifying a pivot table before the support session can be successfully ended. The end result is a much lower cost-per-solution delivered – and one that no doubt required a much higher level of experience and expertise to address.

So, while typical calls to a help desk may cost an average $80 per solution, a specialized partner can deliver solutions for a fraction of this cost.

Aside from getting the terms right, it is also inaccurate to compare the average help desk call with the average “how-to” solution. A help desk handles a disproportionately high number of quick-fix issues (such as password resets, which can average 30 percent or more of all help desk service requests).

Such quick-fix calls skew the average length and cost of a help desk call. If that same help desk examined average minutes spent on just one subset of its data – namely, desktop application and mobile device issues – the numbers tell a very different story.

Lesson 4: A Breakfast Analogy

Training and support are not the same. Training complements support, like milk complements Cheerios, but training is not a viable substitute for support. Still, many IT managers will reason that, since all employees go through training when they are hired and perhaps even periodically thereafter, there is no need for desktop application support. This is flawed for two primary reasons.

First, while training is effective at addressing common and repeated needs, it is highly ineffective – and inefficient – at meeting specialized needs at unpredictable times, which is the very nature of a desktop application support issue. For example, if my company is switching from Lotus Notes to Outlook, it is smart to offer upfront training to teach employees how to attach files, use distribution lists, make calendar entries, etc. – tasks everyone needs to know how to do from the start. But if I cannot figure out why my net present value calculation in Excel is yielding a negative number for the interest rate, training is of no help to me, even if I was the star pupil at every class the company offered.

Beyond that, even a well-trained knowledge worker is highly likely to forget what he/she learned when the time comes to use a key feature or apply a technique within the application or device. Think about the student who studies, aces the exam, and, two months later, cannot remember a lick of what he learned.

Lesson 5: Full-Circle

The presence or absence of quality desktop application and mobile device support feeds a recurring cycle of events.

When support is poor, end-user satisfaction is low. This leads to a low number of calls to the help desk on “how-to” questions and an increase in the need for support, as evidenced by end-users seeking help from peers or other time-consuming sources. This gap in support costs companies an average of three hours of lost productivity per “how-to” issue (see Lesson 1: The Iceberg). But an organization will never see this gap by merely looking at its help desk stats. It is hidden from plain view.

On the contrary, when the gap is bridged with top-notch support, end-user satisfaction increases, as does the number of calls for desktop application and mobile device support. It seems paradoxical, but consider this: When the availability of quality, prompt support becomes known and is then reinforced by experience, the demand shifts from peer support to the newly enhanced help desk. Bridging this gap brings an immediate productivity gain (i.e., winning back the three hours per solution) and a future productivity gain.

An IT manager may ask: Why would I go looking for additional calls? After all, I’m trying to decrease help desk call volume. The real question should be: Why would I allow my company to continue wasting $48 to $196 per “how-to” solution when an alternative model could yield the same solutions for $25?

Have you asked yourself that question? (Jen Darr, Stephanie Maurer)

FIND MORE INFO IN: Download the Full White Paper | Related Case Study | PC Helps eTraining |Desktop Application Support | Contact PC Helps

In an e-mail response, a reader pointed out an even greater obstacle, something he called the infuriation factor.

“The reason I don’t call our help desk is because it is outsourced to desks outside the U.S.,” he wrote. “The ‘Help’ can’t speak English adequately enough to understand or communicate effectively. A problem which should only take five or 10 minutes to resolve sometimes takes as long as an hour and a half.”

He has a point, and it’s a biggie, for sure.

“Desktop application support is often treated as an afterthought, or a small piece of a gargantuan, all-in-one outsourcing deal.”

Most of us have had a frustrating help desk experience or two, where we were placed on hold, forced to listen to tinny ’80s Lite rock, only to be “helped” – eventually – by someone whose English was so-so, and who was proficient only in gatekeeping.

I’m not by any means xenophobic, and I’m not offended if an ATM asks if I’d like to bank in Spanish, Hindi or English, but the point of desktop application support – or any support – is to clear up conundrums. That’s hard to accomplish if the people involved cannot communicate with each other. It’s even more difficult if the help desk employs a tiered structure and bounces callers around until they get a technician who can actually help.

The language issue is a symptom of a larger outsourcing problem. That is, that because the need for desktop application support isn’t easily quantifiable, and because it’s difficult to prove return on investment with such services, it’s is often treated as an afterthought, or a small piece of a gargantuan, all-in-one outsourcing deal. This not only sullies the help desk’s image, it also tarnishes the IT department’s reputation overall.

Recent industry publications have suggested that multimillion dollar outsourcing deals are the stuff of history, and that companies have begun opting for nimbler, best-of-breed help desk outsourcers. Still, the challenges remain: how to change the help desk’s reputation, how to prove its value, and how to keep an eye on the budget. (Jen Darr)

Is your IT department all-in-one or best-of-breed? Tell us in comments or send us an e-mail.

MORE INFO IN: 5 Lessons to Learn Before Outsourcing | Hidden Demand | Desktop Application Support | Contact PC Helps

Fear of asking “stupid” questions is the culprit for many misunderstandings in life, and it clearly plays a standout role in this case. Inserting footers and page breaks shouldn’t be so hard to figure out, right? For a fresh-faced techie, who has immersed himself in software all of his adult life, yes, asking how to fix footers qualifies as stupid.

But for those who started out in business using a typewriter, electric or manual, inserting a footer meant simply typing it at the bottom. Adding a page break was as easy as pulling the paper out of the machine. They did not concern themselves with section breaks, be they even, odd or next page; nor did they care about field codes to insert current date and time, file name or page numbering style. Heck, they may even have brought in a mariachi band for presentation sound effects. (OK, that’s a stretch.)

Anyone who didn’t come of age with a computer has catching up to do, plus a whole lot of maintenance as their existing skills become antiquated.

So, for many, “How do you make the same footer appear on all but the first two pages?” is not an inane question, especially when considering how much has changed in the past 20-odd years. The Internet and computers have had a profound impact on the 21st century, more so than any other technological advance. Each new development requires new skills and understanding. Computer literacy is no longer a special talent; it’s a necessity.

There’s no argument that all corporate workers need technological skills to do their jobs — not developer-level or expert knowledge, mind you, but practical training and ongoing support. Anyone who didn’t come of age with a computer clearly has catching up to do, not to mention a whole lot of maintenance as their existing skills become antiquated.*

The question for CIOs and other IT leaders is: How will you give your employees those skills?

Will you force them “underground” for software support, to huddle and hatch costly, time-consuming workarounds, or will you encourage them to solve their problems productively with the proper training and support? (Jen Darr)

*Source: Ezziane, Zoheir: Information Technology Literacy: Learning and Teaching.

MORE INFO IN: desktop application support | eTraining | contact PC Helps

After more than an hour of trial and error, she couldn’t find the feature she used in previous versions, so she devised a workaround with the space bar to nudge and align.

She asked two of her fellow teachers for help. They couldn’t figure it out either, and they too were using the spacebar fix.

Her opinion of Office 2007 after this experience?

“It sucks. I hate it.”

Teacher A spent more than an hour coming up with her Band-aid workaround. But her solution isn’t a solution at all: She now spends more time on each presentation nudging and aligning.

If she would have called her school district help desk, a consultant would have solved her problem in less than half the time. She could have passed along the information to her colleagues, saving them each an hour. She may have even learned how to use tools that are new to the version.

When asked why she didn’t call the help desk, she said she didn’t think the question was important enough. Besides, she added, she didn’t have time to waste on the phone.

Her opinion of Office 2007 after this experience? “It sucks. I hate it.”

This is typical in workplaces. Even at companies where quality desktop application support is offered, employees hesitate to utilize the service.

One reason is to avoid embarrassment. Many workers have learned their computer skills informally on the job, so they are reluctant to call the help desk for what they perceive is a “stupid” question.

Another reason, and chief among them, is an assumed time investment. Most people have had a frustrating help desk experience or two, where they were placed on hold, forced to listen to tinny, instrumental versions of Cat Stevens hits, only to be “helped” — eventually — by someone who is familiar with everything but proficient in nothing.

So instead, they tap the office software “expert” for help, pulling her away from her job and wasting twice the company effort. Or they fruitlessly scan Microsoft Help files and search the web.

The result is a whopping waste of investment in software. The point of an upgrade is to give users new, usually improved and expanded capabilities. If employees do not have access to training and support, they will naturally come to the conclusion that Office 2007 sucks. That sucks for your bottom line. (Jen Darr)

MORE INFO IN: Office 2007 migration checklist | contact PC Helps

Software migrations will no doubt cause disruptions in at least three areas over several months. But if you approach it with a thought-out plan, you can lessen the sting.

Where’s the File Menu?

The first and most obvious impact will be on your employees. Features they have used for years are suddenly, um, somewhere else. The interface changes in Office 2007 are substantial enough that without training and support before and throughout a migration, even the savviest users will be lost.

“How will an overall decrease in productivity affect your company’s numbers? In a word, nightmarishly.”

Callers are in Queue

Immediately after deployment, employees will bombard the internal help desk with support questions, on top of their regular requests for forgotten passwords and more mailbox size. It’s hard to keep up a balancing act like that, even more so when employees make it over the initial learning hump and begin finding features that are new to the version. That’s 2.0.

The Bottom Line

How will an overall decrease in productivity affect your company’s numbers? In a word, nightmarishly. If John Q. Embeeay is churning out a dozen reports a day using Access and Excel 2003, how long will it take him to get back up to that level using 2007?

Whether it is learning how to use the new ribbon interface or adjusting to file formats, employees and help desks will face a learning curve of some capacity. Productivity, the backbone of a company, will suffer without a migration partner and plan in place. (Jen Darr)

FIND MORE INFO IN: Office 2007 Migration Checklist + Tools | Migration Case Study | PC Helps eTraining |Desktop Application Support | Contact PC Helps

Choosing the right migration partner could mean the difference between the championship or an epic loss.

As with any major investment, IT leaders are responsible for proving the value behind the purchase — no matter the economic climate. In an economic dip like the one we are riding out now, the focus on ROI is doubled.

Most IT leaders realize that a Windows 7 & Office 2007 deployment requires coordination, planning and oversight, and they know which areas need to be assessed and addressed. As a result, most bring in a third party for migration assistance.

Champion your migration and prove ROI with these eight service practices:

1. First-Level Analyst Certification: Providing certified computer consultants (Microsoft Office 2007 and Windows 7 launch partners) results in higher first-call resolution rates based on their core competencies. Information workers are less likely to be placed on hold or passed through a tiered-level support structure. Applying a simple analogy, it is probable that the golfer playing five to six times a week will outperform someone who hits the links a few Sundays a month.
2. Domestic vs. Offshore Staff: The ribbon and overall look of the Office 2007 interface compared to previous versions will test IT staff and information workers. Adding potential language barriers will no doubt raise the challenges.
3. Maintain 24-7 and After-Hours Coverage: Forgo skeleton crews or lower-level support during off-hours and deliver constant, world-class Office 2007 and Windows 7 support and training outlets throughout the entirety of deployment. Many organizations employ staff globally or remotely, in addition to a nine-to-five crew. Don’t penalize employees for working in a different time zone or after hours by providing less-than-stellar service.
4. Deliver Advanced Level Office 2007 & Windows 7 Support: As IT leaders begin to see ROI during the early phases of the migration, information workers will have begun navigating their way around the ribbon and will begin finding additional and more advanced time-saving features. Support avenues should mirror these advanced-level requests and should not be treated with any less urgency than basic-level requests made during the initial migration phase. Avoid tier-structured support models to keep service levels high and reduce worker frustration and downtime.
5. Number of Software and Mobile Device Applications Supported: Requiring a migration partner that is familiar with applications and mobile devices outside the Office suite can be critical to the complexity of Office 2007 calls. Based on statistics collected over the past 18 months, many information workers begin their support requests by referring to what they could do in previous versions and want to see those same steps applied to this new version.* Additionally, Office 2007 and Windows 7 is just as often expected to work in correlation with other applications including BlackBerry and Windows Mobile.
6. Training: Instruction before, during and after a migration is a key element in measuring ROI. Everyone learns at a different pace, so having a multitude of training options is best, i.e., self-service, on-demand, web-based, individual and customized. Being able to identify and deliver targeted training needs, solution-based metrics and measurable productivity gains can justify several portions of an Office 2007 and Windows 7 investment.
7. Planning and Education: Many IT leaders admittedly lack the knowledge that encompasses an Office 2007 and Windows 7 migration assurance plan, hence the reach and popularity of migration partners. With this support and training investment and other day-to-day infrastructure responsibilities IT leaders are tasked with, a migration partner should be expected to deliver a simple, successful solution. Anticipated migration assurance plans should include a readiness checklist, a project and deployment timeline, an information worker education awareness campaign, and excellent support and training — all of which can be easily integrated into the existing IT infrastructure.
8. Call Metrics: Downtime and productivity are key factors in proving ROI for any software or IT-related investment. The question to ask is: If IT leaders commit to purchasing new or updated hardware, servers, software, etc., how will the investment affect business units and add value to the organization’s bottom line? Downtime and productivity levels are two areas that easily can be quantified. With little effort, simple call statistics like response time, abandonment rate, hold times, and average first-call overall resolution percentages can be measured and delivered.

*Knowledge workers at 10 Fortune 1000 organizations (clients of PC Helps) were surveyed November 2008 through April 2009, and were asked to quantify the amount of time they would have spent resolving issues such as importing data into a file from another source in Access 2007, tracking changes in a Word 2007 document, repairing a damaged Excel 2007 file, and hundreds of other Office 2007-related software questions without the services of PC Helps Support, LLC.

MORE INFO: March Migration Madness — click here for a top-seeded team and strategic game plan | PC Helps Info Center | Contact PC Helps

Poka-yoke is Japanese for “mistake-proofing.” Think of the “In Case of Fire Break Glass” boxes found in office buildings. Because they include a wee stick with which to break said glass, they would qualify as poka-yoke.

Best of all, your employees will experience minimal downtime and very little lost productivity.

In business, Schrage explains, poka-yoke is the “simplest, cheapest, and surest way to eliminate foreseeable process errors.” He urges managers to perform a poka-yoke audit of their own department.

“What are the persistently simple — and simply persistent — dumb mistakes we make that our technologies can help us catch and destroy?” he asks.

Here’s where I believe IT managers should start: the help desk.

Say your company is planning an Office 2007 migration, and you, as CIO, have decided that because of the current economic climate, assistance isn’t needed. After all, your reliance on internal help desk staff during previous Office upgrades didn’t turn out disastrously.

You can take a number of approaches:

• Train your existing IT staffers on Office 2007, and hire extra workers to handle the migration, which would include extensive training and standard benefits;

• hire temps or rely on your current all-in-one outsourcer to get you through it;

• or, bring in a specialized migration partner.

As you may have heard, Office 2007 is radically different from earlier versions. Even the most experienced users will have trouble performing basic tasks like saving documents.

Which one do you think qualifies as the simplest, the cheapest and surest?

In principle, working with the staff you have and hiring a few more keeps the control in your hands, but doesn’t make sense financially or logistically. You will need to train new employees on the entire Office 2007 suite, pay benefits, and dole out extra expenses for an after-hours support skeleton crew.

Such a significant time and money investment (at about $85 per call) does not make sense when you consider that you have no guarantee the new FTEs and your existing IT staff will be able to cover a full-swing migration while maintaining their regular duties. Plus, your new employees will be generalists, supporting only a dozen or so applications. The average peak hold time for this solution is nine minutes, and the call abandonment rate is 10 percent.

At an average of $96 a call, temps are pricier than full-timers, and don’t even deliver better service (15 percent abandonment rate). A temp solution offers generalist support and an average 15-minute hold time during peak hours. It does not provide training, advanced Office 2007 support, or awareness campaigns.

Choosing a big-box outsourcer seems like a smart option if you already contract with one for other services. At $59 on average per call, this option is cheaper than hiring temps and full-timers. Also, some all-in-ones offer training in conjunction with a migration. The downside: The staff is mostly generalists whose first language is not English. Some big outsourcers employ tiered-model desks as well. When you factor in the 10-minute peak hold time and 15 percent call abandonment rate, this option loses its shine.

The last option, a migration partner, is often dismissed as an unnecessary expense, especially when budgets are sparse. However, if you choose the right outsourcer, you will get domestic Microsoft-certified consultants; support for more than 160 applications, including advanced-level Office 2007; training courses and awareness campaigns; after-hours support; no hold time; a call abandonment rate of .01 percent; and a 91 percent first-call resolution rate. Average cost per solution with this option is $25.

Here’s the poka-yoke: By hiring a migration partner, you will not have to hire extra staff (or fire them once it’s complete); you will not need to train your staff to an expert Office 2007 level; you will not have to pay overtime when call volume balloons during the initial migration phase; and, best of all, your employees will experience minimal downtime and very little lost productivity.♦

Read Schrage’s full article.

Download your free migration readiness kit.

MORE INFO IN: Office 2007 Migration Case Study | Office 2007 Migration Assurance Program | Migration Readiness Checklist | Migration Competitive Analysis | Contact PC Helps