Skip to content

Be more productive and save time with CloudM Migrate 4.0

 

Introducing CloudM Migrate 4  

Migrate 4 builds on the longstanding success of its predecessors, but makes bold strides to advance its feature set and user experience. 

Revamped UI

Migrate 4 features a new and improved UI that is easier and more intuitive to navigate, enabling users to complete their work more quickly and efficiently. 

play_circle
Video: Migrate 4 sports a much cleaner UI.

Efficiency at the heart

The theme of boosting efficiency runs through this major release: with Migrate 4, we move away from the concept of having configurations and child configuration. Instead, migrations are now managed as projects with batches. This saves time and removes complexity as connections to source and destination platforms can be managed centrally, enabling you to use them across multiple projects, reducing the need for manual intervention and duplication.

Image: With Migrate 4, migrations are managed in batches to save time and remove complexity.

Incorporate multiple source platforms in one project

With Migrate 4, it is possible to add multiple source platforms to a project. This is a more holistic approach to migrations, making it easier and quicker to consolidate several source platforms into one productivity suite such as Google Workspace or Microsoft 365.

In addition, each source platform can have multiple batches. Batches can be created to only contain certain item types, making it easy to prioritize your data and organize the migration. 

Pick up incomplete projects

Focussing on ease of use, a new tab for incomplete projects allows users to create projects in stages. The project draft is saved, ready to be accessed and completed at a later date. 

Image: Migrate 4 enables you to create your projects in stages, allowing you to pick them back up via the incomplete projects tab.

Know your sources

Migrate’s environment scan has always been a key feature thanks to actionable insights it gives. With the new release, the scan can now be run at source platform level as well as batch level. The former enables users to scan the entire source at the very beginning of a migration project, while the latter gives better insight into how much data is in a batch and how long it will take to migrate. Both equip users with more visibility and insight into the project. 

Image: In Migrate 4, the environment scan can run at badge as well as source platform level.

There’s more!

There are a host of other improvements to CloudM Migrate that make it that much easier to manage migrations, such as added filters for migration batches and relocation of tabs to improve navigation. 

A full list of enhancements and improvements can be found in the release notes for Migrate 4.0. Check them out here.

About Version 2 Digital

Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.

Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.

About CloudM
CloudM is an award-winning SaaS company whose humble beginnings in Manchester have grown into a global business in just a few short years.

Our team of tech-driven innovators have designed a SaaS data management platform for you to get the most from your digital workspace. Whether it’s Microsoft 365, Google Workspace or other SaaS applications, CloudM drives your business through a simple, easy-to-use interface, helping you to work smarter, not harder.

By automating time-consuming tasks like IT admin, onboarding & offboarding, archiving and migrations, the CloudM platform takes care of the day-to-day, allowing you to focus on the big picture.

With over 35,000 customers including the likes of Spotify, Netflix and Uber, our all-in-one platform is putting office life on auto-pilot, saving you time, stress and money.

Migrating from SharePoint to Google Drive with CloudM

With CloudM Migrate, you can seamlessly migrate content, sites and permissions from SharePoint into Google Drive and Shared Drives.

Migrate offers both self-hosted and hosted deployment versions, providing flexibility based on your organization’s needs. Our pre-migration environment scan ensures that any potential issues are addressed before they impact the migration, making the process more reliable and streamlined.

Addressing SharePoint-to-Google migration challenges

Moving from SharePoint to Google involves some structural differences. Google Drive organizes files into My Drive and Shared Drives, while SharePoint uses centralized team sites for data storage and collaboration. Google Workspace’s flat, intuitive structure makes it easier for teams to collaborate in the cloud, and Shared Drives enable centralized content management with granular permissions.

Additionally, Google Drive is designed to handle larger file volumes more efficiently than SharePoint, which can sometimes struggle with performance issues when managing large datasets.

CloudM’s seamless migration process

Cloud-native migration solution

CloudM Migrate can scale to handle migrations of any size, from small departments to entire enterprises with hundreds of terabytes of data. Migrate automates the transfer of files, file and folder permissions, and folder structures, ensuring a smooth and reliable transition to Google Drive and Workspace.

Enhanced collaboration and permission control

If you're migrating specific SharePoint sites, Migrate allows you to map their contents directly into Google Shared Drives, enabling easier collaboration and better control over permissions. In addition, the tool is equipped to handle Google Drive limitations, such as file count restrictions within Shared Drives, alerting you ahead of time to avoid issues.

Zero infrastructure requirements  

Since CloudM is available in both self-hosted (on-premise) and hosted (SaaS) versions, you have the option to choose a solution that best fits your requirements. The self-hosted version provides full control over your migration, while the hosted version removes the burden of infrastructure management so your IT team can focus on higher-priority tasks.

For larger migrations, Migrate offers the ability to scale its resources thanks to its multi-threaded architecture, allowing for faster and more efficient transfers, whether dealing with hundreds or millions of files. This scalability ensures that no matter the size of the migration, Migrate can perform the task quickly and securely.

Pre-migration environment scan

Before migration begins, Migrate offers a pre-migration environment scan that simulates the process. This scan helps identify potential errors, bottlenecks, and unsupported file types, providing a clear overview of your data before it’s transferred. The pre-scan makes troubleshooting easy, minimizing issues during the actual migration process and ensuring that your migration is as efficient as possible.


Simple, fast, scalable

Migrate is designed to make SharePoint to Google Drive migrations straightforward, no matter the scale. Whether you’re migrating small teams or an entire enterprise, the tool’s intuitive interface, robust automation, and flexible deployment options make the process quick and cost-effective.

Conclusion

Migrating from SharePoint to Google doesn’t have to be complex. With CloudM Migrate, you have a solution that simplifies the process while ensuring your data is migrated securely and accurately. Ready to start your migration? CloudM is here to guide you every step of the way.

About Version 2 Digital

Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.

Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.

About CloudM
CloudM is an award-winning SaaS company whose humble beginnings in Manchester have grown into a global business in just a few short years.

Our team of tech-driven innovators have designed a SaaS data management platform for you to get the most from your digital workspace. Whether it’s Microsoft 365, Google Workspace or other SaaS applications, CloudM drives your business through a simple, easy-to-use interface, helping you to work smarter, not harder.

By automating time-consuming tasks like IT admin, onboarding & offboarding, archiving and migrations, the CloudM platform takes care of the day-to-day, allowing you to focus on the big picture.

With over 35,000 customers including the likes of Spotify, Netflix and Uber, our all-in-one platform is putting office life on auto-pilot, saving you time, stress and money.

Migrating from Box to Google Drive: what you need to know

The telltale signs of a successful migration from Box to Google Drive are minimal disruption and a smooth adoption process for your end users. In this guide, we’ll walk through the key steps and considerations to keep in mind during the migration process using CloudM Migrate, a powerful tool that simplifies moving your data.

1. Prepare your source

Before diving into the migration, it’s crucial to prepare your source environment — in this case, Box — to avoid surprises that can cause issues down the road.

What to keep in mind

When migrating data from Box to Google Drive, there are several factors to consider to ensure a smooth transition:

Document permissions

Migrating permissions can be tricky. It’s important to ensure that shared folders, documents, and their permission levels are carried over correctly. CloudM Migrate can migrate documents with their associated permissions, so files will remain accessible to the same users.

Folder structure

Migrating your folder structure is crucial, especially for teams that rely heavily on file organization within Box. Fortunately, CloudM Migrate allows for the preservation of the folder hierarchy, ensuring everything remains as familiar as possible for end users.

Less is more – clean up before the move 

A migration is an excellent opportunity to tidy up your data. Over time, files that are no longer relevant or necessary can clutter your storage and slow down progress. With CloudM Migrate, you can ensure only required data gets transferred by:

Targeting specific users or folders: you have the flexibility to migrate specific users or groups of users to a Shared Drive or personal account. CloudM Migrate also allows targeting a specific folder within a user’s Box account.

Applying date filters: to avoid moving unnecessary data, you can set date filters to migrate only files that were created or modified within a specific date range. 

2. Consider the specifics of your destination

While Google Drive is a powerful and flexible platform, it’s important to understand its limitations to avoid any issues post-migration.

Google Shared Drive object limits

As of July 2024, Shared Drives in Google Workspace have expanded capabilities. Shared Drives can now have:

  • 100 levels of nested folders
  • Up to 500,000 items

While this increased limit provides more flexibility, it’s essential to keep track of how deep and complex your folder structures are during the migration to avoid hitting these limits.

Google folder depth limit

Google Drive limits the depth of folder structures, which could be a concern if your current Box environment has extremely deep folder trees. Although Shared Drives now allow for up to 100 levels of nesting, consider simplifying your folder hierarchy where possible to make navigation more intuitive for your team.

3. Execute the migration

Once your source environment is prepared and you’ve considered the limitations of your destination, it’s time for the actual migration.

1. Configure the source

When using CloudM Migrate, you’ll authenticate Box using JWT (JSON Web Token) authentication, which is a more secure method than some alternatives. This ensures that your data transfer is encrypted and secure during the migration process.

2. Configure the destination

Next, you’ll configure Google Drive as the destination. Ensure that permissions are set properly and that Shared Drives or user accounts are ready to receive the data.

3. Select items

At this stage, you can choose which users to migrate from Box to Google Drive. This could be individual users, groups of users, or all users across your organization.

4. Select content

Here, you’ll specify which data you want to migrate, whether it’s all user data or only specific files. This step allows you to filter content based on the user or folder.

5. Scan the environment

Running a scan of both the Box and Google Drive environments is essential to identify any potential issues, such as file size limits, unsupported file types, or naming conflicts.

6. Run the migration

Once the environment scan is complete, it’s time to run the migration. CloudM Migrate handles the heavy lifting, transferring data securely from Box to Google Drive.

7. Review the results

After the migration is complete, it’s important to review the results and ensure all data, permissions, and structures were transferred correctly. This is where you’ll verify that everything is in place for a smooth transition.

8. Run delta migrations

To ensure you haven’t missed any changes or updates that occurred during the migration window, run one or several delta migrations. This will capture any files that were modified or created after the initial migration began.

Conclusion 

Migrating from Box to Google Drive is a critical task for any organization looking to streamline its cloud storage. By following these steps and utilizing CloudM Migrate, you can ensure a smooth and efficient migration process that keeps your data, permissions, and structures intact while avoiding common pitfalls. 

If you are facing a particularly complex migration scenario or simply don’t have the internal resource and experience to tackle your upcoming migration project alone, CloudM are happy to help. We offer serviced migrations as well as customer-led consultancy workshops to ensure your success. 

About Version 2 Digital

Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.

Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.

About CloudM
CloudM is an award-winning SaaS company whose humble beginnings in Manchester have grown into a global business in just a few short years.

Our team of tech-driven innovators have designed a SaaS data management platform for you to get the most from your digital workspace. Whether it’s Microsoft 365, Google Workspace or other SaaS applications, CloudM drives your business through a simple, easy-to-use interface, helping you to work smarter, not harder.

By automating time-consuming tasks like IT admin, onboarding & offboarding, archiving and migrations, the CloudM platform takes care of the day-to-day, allowing you to focus on the big picture.

With over 35,000 customers including the likes of Spotify, Netflix and Uber, our all-in-one platform is putting office life on auto-pilot, saving you time, stress and money.

Introducing the NIS2 directive and DORA regulation

Cybersecurity is taking centre stage for the EU, with two pieces of legislation coming into place. 

The NIS2 directive and Digital Operational Resilience Act (DORA regulation) both focus on cybersecurity. But the audiences and goals are different.

The NIS2 directive ensures a high cybersecurity standard across all EU member states. It targets organizations in sectors with a high impact on our daily lives – ‘essential entities’ such as energy, transport, and finance, and ‘important entities’ like postal services, manufacturing, and food production.

The DORA regulation has a narrow focus on financial services. It aims to increase resilience and cybersecurity for 21 types of financial entities and ICT third-party service providers. 

If you’ve already put two and two together, you’ll have spotted the overlap between these two pieces of legislation. So, do certain financial services firms need to maintain compliance with both?

In this guide, we provide a top-level overview of NIS2 and DORA, including who they apply to and how they overlap. We also share pointers on maintaining NIS2 and DORA compliance and keeping your business cybersecure.

Key differences between the NIS2 directive and DORA regulation

Cybersecurity is at the centre of both the NIS2 directive and DORA regulation. But there are several differences between the two.

Look deeper into DORA requirements, and you’ll see it focuses on key areas such as ICT and third-party risk management, ICT incidents, digital operational resilience testing, information sharing and third-party provider oversight.  

NIS2 requirements include 10 key elements all companies need to address. These include incident handling, supply chain security, and vulnerability handling and disclosure. 

Resilience testing looks different under both legislations – DORA demands annual resilience testing programs and a threat-led penetration test every three years. NIS2 only requires security audits every two years. 

Directive vs regulation

The biggest difference between NIS2 and DORA is their legal structures. NIS2 is a directive and DORA is a regulation, which means they’re enforced differently.  

Directives give you the direction of travel. But it’s down to member states to translate these into national law before they can be applied. In the case of NIS2, EU member states have 24 months from its publication in December 2022 to introduce national laws, giving a deadline of October 2024. 

This could mean mandated businesses based in two separate EU member states follow different standards for the same directive.

As a regulation, DORA needs to be applied uniformly across all EU states when it comes into force on 17 January 2025.

Where do NIS2 and DORA overlap?

Both the NIS2 directive and DORA regulation demand clear policies, processes and tools for handling cybersecurity risk.

Financial penalties

Fines are heavy for NIS2 and DORA non-compliance – up to 2% of total annual turnover.

Incident reporting

Reporting requirements for NIS2 and DORA are the same – Initial incident reports are due within 24 hours, detailed reports within 72 hours and final reports within one month for both. Business continuity, disaster recovery and backup requirements are also included in both.

Data backup and business continuity

Finding secure ways to back up and manage your business data will help you maintain DORA and NIS2 compliance.

Leadership and risk management

Both pieces of legislation require strong leadership. Start by assigning someone to lead on compliance, enforcing policies, procedures and behaviours, and reviewing cybersecurity gaps in your operations.

NIS2 or DORA – which legislation applies to me? 

The DORA regulation is ‘lex specialis’ – meaning more specific rules (like those laid out in DORA) take precedence over more general rules (like those in NIS2). If your organisation falls under NIS2 and DORA rules, prioritise DORA.

For 21 types of financial entities – including credit institutions, banks, payment institutions and investment firms – DORA is the primary legislation. Check whether your organisation is one of these 21 types so you know which rules to follow.

Ensure compliance with CloudM Backup

A reliable backup tool can help keep your business running smoothly and buffer the effects of a cybersecurity threat. 

CloudM Backup stores your vital business data reliably and securely. We’re industry leaders for data backups, with secure encryption in transit and at rest, and compliance with ISO 27001. You always get a clear view of important information – with access to a dashboard containing key stats and notifications about your data. 

Choose from broad or granular restoration options that enable you to mass restore an entire dataset, or single folders and items. Flexible, reliable data backups and recovery to fit you.

About Version 2 Digital

Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.

Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.

About CloudM
CloudM is an award-winning SaaS company whose humble beginnings in Manchester have grown into a global business in just a few short years.

Our team of tech-driven innovators have designed a SaaS data management platform for you to get the most from your digital workspace. Whether it’s Microsoft 365, Google Workspace or other SaaS applications, CloudM drives your business through a simple, easy-to-use interface, helping you to work smarter, not harder.

By automating time-consuming tasks like IT admin, onboarding & offboarding, archiving and migrations, the CloudM platform takes care of the day-to-day, allowing you to focus on the big picture.

With over 35,000 customers including the likes of Spotify, Netflix and Uber, our all-in-one platform is putting office life on auto-pilot, saving you time, stress and money.

What is HIPAA and how can you comply?

The process of managing patient health data isn’t the same as it was a few years back. Records aren’t just stored in filing cabinets and on company devices anymore, they’re in the cloud.

The Health Insurance Portability and Accountability Act of 1996 (HIPAA) standardized how private health information (PHI) and electronic private health information (ePHI) is managed. The act details how organizations should keep patient information safe and secure, inside and outside healthcare practices.  

If you deal with PHI or ePHI – whether that’s as a healthcare provider or a business working with healthcare providers – you need to comply with HIPAA rules. This guide gives you a whistlestop tour of HIPAA compliance requirements

But before we dive into the details of how you can ensure you comply with HIPAA, let’s take a quick look at what’s at stake.

The cost of non-compliance

Failure to comply with HIPAA requirements can result in fines up to $68,928 per violation per year, civil lawsuits, and criminal charges.

 

4.9 million

people affected by a data loss at Tricare Management.
 
$115 million
settlement following a class action lawsuit against Anthem, Inc, in addition to a $15 million fine for HIPAA violations.
 
$2 billion
total HIPAA penalties issued since 2003.

Depending on the severity of the violation, HIPAA fines can seriously hurt an organization financially. But there’s more. If an organization is found to have been lax with keeping sensitive data safe, they will be the focus of public scrutiny which can severely damage the brand’s reputation and further hinder recovery and operations.

Let’s look at how you can avoid this by examining the rules and requirements of HIPAA.

HIPAA rules: an overview

The aim of HIPAA is to keep private health information, in all its forms, safe. For mandated organizations, this information must remain confidential both inside and outside healthcare facilities. If HIPAA rules are breached, organizations could face penalties ranging from a few hundred dollars to tens of thousands depending on the severity of the violation. 

Private health information could include a patient’s medical conditions, the healthcare they receive, and payment for this care. It’s health data that’s individually identifiable for the patient.  

There are five parts to HIPAA legislation, known as titles. Each section focuses on a different aspect of using healthcare data. Where the first title regulates group and individual health insurance policies, the second title establishes privacy and security standards for protected health information. Here’s the full list of titles: 

  1. Healthcare access, portability, and renewability 
  2. Preventing healthcare fraud and abuse, administrative simplification, and medical liability reform 
  3. Tax-related health provisions governing medical savings accounts 
  4. Application and enforcement of group health insurance requirements
  5. Revenue offsets governing tax deductions for employers 

In the next section, we focus on the second title because this is where guidance on keeping ePHI secure can be found under the Security Rule. 

HIPAA rules apply to two different groups: covered entities and business associates. Covered entities are organizations that provide treatment, healthcare plans, or deal in payments (healthcare clearinghouses). Business associates are companies working for covered entities that have access to PHI and ePHI – cloud storage companies, billing providers, and outsourced IT businesses. HIPAA compliance requirements for the Security Rule vary slightly between these two groups, but both must follow the safeguarding rules outlined in the next section.

The Security Rule

Effective HIPAA compliance relies on multiple policies, processes, and tools. The Security Rule is a core tenet of HIPAA legislation, which focuses solely on the protection of ePHI. This isn’t just relevant for healthcare providers, but for third parties that come into contact with electronic health data through their partners. 

The Security Rule requires organizations to protect ePHI through the following safeguards. 

Administrative safeguards include risk analysis and mitigation strategies (plus regular process and policy evaluations), assigning security personnel, enforcing access management policies, proper training, management, and sanctions for your workforce. 

Physical safeguards mean limiting access to physical data storage facilities, and policies that guide the use of devices and workstations. This could mean defining how work phones and laptops are used to access or manage ePHI, and how regularly passwords need to be updated.   

Technical safeguards focus on the use of technology and digital tools. This includes setting up access and audit controls and monitoring access using hardware, software, and procedures. It also includes controls that prevent ePHI from being altered or destroyed incorrectly and security measures that protect against unauthorized access to ePHI transmitted over an electronic network (encryption).

With the help of these safeguards, you must: 

  • Uphold the confidentiality, integrity, and availability of the ePHI you create or manage as an organization
  • Identify and protect against reasonably anticipated threats to the security and integrity of information
  • Protect against reasonably anticipated impermissible uses or disclosures of this information
  • Ensure compliance from your workforce

Organizations also need to have a data backup plan, complete with procedures – like an established backup schedule – to create, maintain and restore exact copies of ePHI. This should be supported by documentation, which verifies the creation of backups and their secure storage. And data should be stored in a physical location, separate from the data source. 

 You might find it helpful to create an HIPAA compliance checklist, complete with the guidance above, so you can make sure your organization is hitting the mark. And don’t forget to take a few moments to review the full HIPAA security rule guidance on the US Department of Health and Human Services website, too. 

Make HIPAA compliance seamless with CloudM Backup

Keeping a clear view of the private information you create and maintain is essential for HIPAA compliance. But you can’t have eyes everywhere – and without sturdy tools and processes in place, risks can slip through the net. 

This was the case for a behavioral healthcare provider in Maryland. The organization failed to provide good risk assessment evidence, implement robust security measures, and enforce policies and procedures for reviewing records after 14,000 patients had sensitive information stolen. This breach resulted in a $40,000 fine for violating multiple HIPAA rules.

You can avoid similar costly errors by implementing CloudM Backup. Our software helps you maintain HIPAA security rule compliance by enabling you to create regular, secure, and retrievable backups of ePHI. Information is stored in your infrastructure, and you can restore data quickly should a malicious or accidental loss occur. 

Automation features mean data retention and backup policies can be applied automatically – saving you and your team time on manual admin while ensuring consistent and reliable data management. We use the encryption standard AES-256 and are ISO 27001 certified – so you can trust us to take your and your customers’ data seriously. 

Our product is robust but flexible. You can set up bespoke policies that meet local data retention requirements, and tailor CloudM Backup to meet the needs of your organization (and HIPAA rules).  

Find out about HIPAA-compliant cloud backup and disaster recovery software

Book a call with our Backup specialists today.

About Version 2 Digital

Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.

Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.

About CloudM
CloudM is an award-winning SaaS company whose humble beginnings in Manchester have grown into a global business in just a few short years.

Our team of tech-driven innovators have designed a SaaS data management platform for you to get the most from your digital workspace. Whether it’s Microsoft 365, Google Workspace or other SaaS applications, CloudM drives your business through a simple, easy-to-use interface, helping you to work smarter, not harder.

By automating time-consuming tasks like IT admin, onboarding & offboarding, archiving and migrations, the CloudM platform takes care of the day-to-day, allowing you to focus on the big picture.

With over 35,000 customers including the likes of Spotify, Netflix and Uber, our all-in-one platform is putting office life on auto-pilot, saving you time, stress and money.