So, you’ve decided to move your on premise email system to Office 365/Exchange Online for cost savings, higher security, and scalability. However, before you begin the migration, a question you should ask is; does my organization journal email for compliance, legal, or business requirements? If your company does, then read on.
Are you planning your move to Office 365 and struggling to manage your legacy email archive? If so, download this new white paper by Archive360 that concisely describes the challenges that you face and the best practice. Some of the challenges are:
Infrastructure Modernization is a trendy new phrase you will hear from industry experts and read about in IT-related articles. In simple terms, infrastructure modernization describes a major shift taking place from on premise applications to cloud-based applications. When properly deployed, new cloud-based applications can dramatically reduce your CAPEX spending in favor of low cost software services.
ATLANTA – September 20, 2016 Archive360™, the leading provider of email archive migration software, today announced that it will be showcasing its Archive2Anywhere™ compliant email archive migration solutions and Archive2Azure™, the industry’s first Microsoft Azure –based long term compliance storage solution for low-touch, inactive, and grey data during next week’s sold-out Microsoft Ignite Conference, in Booth 2144. The solutions, which quickly transform legacy email archives and other unstructured grey data into compliant, cloud-based archive environments, provide collection, migration and long term retention for archived and unstructured data for compliance, legal and business requirements.
A long running issue with Exchange systems is managing inactive mailboxes. An inactive mailbox is simply a mailbox that is associated with a departed employee. With on premise Exchange systems it was relatively straight forward – let them sit indefinitely, or for a specified time period (e.g. 3 years), for legal, regulatory, or business reasons.
If you’re moving a legacy email archive to Office 365, chances are good that you also have Exchange journal data to move as well. If you do, it’s likely that the total amount of journal data is equal to or greater than the total size of your email archive.
With regards to Office 365, you might be wondering where the journal data is stored. It comes down to two possibilities; move the journal into the Personal Archive of an Office 365 active mailbox, or create separate Office 365 mailboxes (e.g. Journal Mail 001, Journal Mail 002, Journal Mail 003) and move the journal data for groups of custodians into those. This practice is called "journal splitting”. To many, an unknown concept that raises many questions, the most important being; is journal splitting the best practice for your organization’s regulatory or legal needs? The answer is it depends… Let’s break it down so you have all the facts before you make a migration decision on your journal.
Companies that transmit data from Europe to the US have become vulnerable to unexpected financial costs from EU members. Brexit may be the most visible headline from the EU but a lesser-known threat poses more of a compliance concern. We reported last Fall about the potential fallout expected after the EU’s decision in the Schrems case invalidating the Safe Harbor Agreement and what US companies could expect were they not to change course before the EU’s January 2016 deadline. [i] Specifically, our concern was that an individual EU member State could impose its own rules and fine companies in the absence of a common plan subjecting US companies to potentially 28 different sets of privacy rules. Germany has now fired the first shot in this new privacy skirmish.
Many organizations are moving their Exchange email systems from on premise to the cloud via Office 365 to save cost, simplify operations, and increase ease of use and productivity for their employees. Migrating the contents of an on premise Exchange email system to Office 365 is straight forward and can be accomplished in a relatively short amount of time. But what if your organization also has an on premise legacy email archiving system as well?
How much unstructured data does your organization actually have? Do you have any idea? Could you find and search through all of your organization’s data in response to an eDiscovery request or regulatory information request - quickly? What’s the downside if you can’t?
Microsoft FastTrack was designed to help you move your on premise Exchange email system to Office 365 “smoothly and with confidence”. But, when you read the “fine print” you discover that FastTrack will NOT migrate email archive data, including compliance-related journal data. The problem with this oversight is that most organizations planning to migrate to Office 365 similarly have a legacy email archive that should also be migrated. In fact, in a recent survey by Osterman Research, 64% of Office 365 migrations include a legacy email archive, so this lack of support is a major “road block” (or at least speed bump) to fully migrating to Office 365.
Are you familiar with the concept of Exchange Journal Data? Many are not so let me give you a quick refresher. Journaling has been a mainstay of the Exchange Server for many years. In fact, it was introduced in a Service Pack for Exchange 2000 and has been a feature ever since. Journaling is enabled per mailbox and sends a copy of every message sent or received to a designated storage location, in many cases an email archive.
Lawsuits have become a (high) cost of doing business for most organizations. Because of that, eDiscovery response should be proactively planned for to ensure the lowest possible cost to the company.
Believe it or not, email archives and Zombies have quite a lot in common. Below is my list of common archives/zombie issues. I would love to hear your horror story with regards to a legacy email that you’ve had problems with during a migration. Please submit below in the comments.
Freshly published this week is a new research white paper published by Osterman Research and Archive360, titled “Migration to Exchange Online and Office 365: A Step-by-Step Guide”. For Exchange Administrators, Managed Service Providers and anyone involved with email migration, this is a “must read”. The white paper contains tons of useful tips regarding migration planning and best practices. It also includes some startling facts regarding email archive migration. (See figure below).
Topics: Office 365
First, what is an inactive mailbox?Simply put, an inactive mailbox is one that is no longer used because the mailbox owner (employee) has left the company, leaving the mailbox orphaned. It is very common for mailboxes to remain in the Exchange system after an employee leaves the company for several reasons including standard company practices, lack of company processes, legal reasons i.e. anticipated lawsuits, and regulatory concerns. These orphaned mailboxes can become an issue later, for example if an organization decides to move their email system to the cloud.
First, let me thank the Microsoft Partners that have responded to my previous two blogs titled "PowerShell Advantage: Real Time Active Directory Integration with Email Archive Migration" and "PowerShell: No Experience Required – For Email Archive Migrations to Office 365" covering archive migrations via PowerShell. I was surprised at such a great response. In today's blog I want to continue to build on the partner benefits of PowerShell and archive migrations.
What are mailbox stubs and what should I do with them?
Email stubs (or pointers) are a confusing concept, but because the concept is so important when migrating the on premise email to Office 365, it’s a good idea to look at them in a little more detail.
Topics: Office 365
I’ve been talking to many Microsoft Office 365 Partners asking them why they almost always avoid the companion email archive migration project. One of the most common answers is: "we just don't have the knowledge of the many email archives and their particular idiosyncrasies; let alone attempt to migrate one of them." This answer baffled me since an archive migration can generate 3-5x the revenue of a single project not to mention, if done correctly, can generate a 90% profit. You may be asking yourself how….? Well, let me explain.
Are you excited about moving your on premise Exchange Server to Microsoft Office 365? Office 365 is an exciting cloud-based solution for all your company’s communication and collaboration solutions. However, before you decide to migrate your on premise Exchange Server to Office 365, there is one important question you must address; Does your current on premise Exchange Server also have an email archive attached?
Topics: Office 365
Hi, I'm Joel Bennett, and I'd like to take a moment to talk to you about PowerShell, how it's changing the way companies are migrating their email archives (particularly when they're migrating to Office 365), and why here at Archive 360 we are redesigning our management tools from the ground up.
Topics: Office 365