Kazuya Mishima
My feedback
19 results found
-
1 vote
An error occurred while saving the comment -
1 vote
-
1 vote
-
1 vote
-
1 vote
-
1 vote
-
1 vote
-
1 vote
-
1 vote
An error occurred while saving the comment Good overview. Moving from Gmail to Microsoft 365 is a common step once a company wants tighter compliance, Teams, SharePoint and Outlook in one place. Whether it's the right call really depends on the team, but the migration itself is where most people feel the pain.
Where people usually struggle: email moves over easily enough, but calendars, contacts, shared mailboxes, Google Groups and aliases are where things get fiddly, especially with a deadline and a mix of users on different devices.
The free/manual route, roughly:
1. Add and verify your domain in the Microsoft 365 admin center and create the users.
2. Use the built-in Google Workspace (Gmail) migration in the Exchange admin center. It needs some Google Cloud setup (a project, service account and API access), so follow Microsoft's current docs. For a handful of mailboxes, IMAP migration is simpler but moves mail only.
3. If you go the IMAP route, export calendars (.ics) and contacts (.csv) separately and import them by hand.
4. Move Drive files by download and re-upload to OneDrive.
5. Lower your DNS TTL a day or two ahead, then switch the MX records once mail is migrated.
6. Keep Google Workspace active for a few weeks as a safety net.Common mistakes with the manual way:
- Switching MX records before mailboxes have finished copying, so new mail lands in the wrong place.
- Using IMAP and forgetting it doesn't carry calendars or contacts.
- Missing aliases, groups and shared calendar permissions.
- Hitting throttling or 2FA/app password issues halfway through a big mailbox.
- Cancelling Google too early, before checking everything arrived.
- Skipping a 1-2 mailbox pilot, so problems only show up after cutover.If you'd rather skip the manual effort, the Kernel Google Workspace to Office 365 Migration Tool can move Gmail, calendars, contacts and Google Groups to Microsoft 365 with folder structure intact, and the free trial lets you test a small batch first.
Learn More: https://www.nucleustechnologies.com/g-suite-to-office-365/ -
2 votes
-
1 vote
An error occurred while saving the comment This is a useful overview, but I’d still suggest trying the native recovery options before jumping straight to a third-party repair tool.
If you have a healthy .bak backup, restoring it should usually be the first option. If a backup isn’t available, I’d run DBCC CHECKDB to understand the type and severity of the corruption before attempting any repair. It’s also a good idea to work on a copy of the database files rather than experimenting with the only original MDF/NDF files.
The difficult part is when the database is stuck in Suspect or Recovery Pending mode, the MDF/NDF file can’t be attached, or CHECKDB reports serious corruption. That’s where manual recovery can become risky, especially if repair options could result in data loss.
For those situations, I’d also consider Kernel for SQL Database Recovery. It supports recovery from corrupt MDF/NDF files and lets you preview recoverable database objects before saving the recovered data.
Visit to know more: https://www.nucleustechnologies.com/sql-recovery.html
-
1 vote
-
1 vote
-
1 vote
An error occurred while saving the comment Yes, a Microsoft 365 tenant migration can be safe, but the planning matters more than the tool itself. Before moving anything, I'd make sure the source and destination users are mapped correctly and that permissions, licenses, mailboxes, OneDrive, and SharePoint are ready.
For smaller migrations, some work can be done manually using Microsoft 365 admin tools and PowerShell. The problem is that manual migration gets harder with a large number of users and workloads. Common issues include incorrect user mapping, missing permissions, duplicate data, and forgetting to migrate newly created data after the first pass.
I'd also recommend doing a small test migration first and checking the migrated data before moving everyone. Keeping a backup of the source data until everything is verified is another good precaution.
For larger migrations, Kernel Microsoft 365 Migration is another option to consider. It can reduce the manual work involved in moving Microsoft 365 data between tenants and is useful when dealing with larger migration projects.
https://nucleustechnologies.com/microsoft-teams-migration/ -
1 vote
An error occurred while saving the comment If a mailbox is lost or deleted, I’d first check Exchange’s built-in recovery options and any recent backup. If the mailbox was only recently deleted, it may still be recoverable through the Exchange environment without needing third-party software. A backup is also the safest option if you have one available.
The situation is different when the mailbox or Exchange database is corrupted, inaccessible, or the normal recovery options no longer work. In that case, I’d avoid making changes to the original data and work with a copy. A recovery tool that can scan the Exchange data and preview the available mailbox items is much safer than blindly exporting everything.
I’d also look for selective recovery, since you may only need certain emails, folders, contacts, calendars, or attachments. If multiple mailboxes are affected, batch recovery can save a lot of time. Previewing the data before recovery is especially useful for confirming that the required mailbox items are actually there.
If you want to try a free option first, Free Kernel’s Exchange Recovery is worth checking. It lets you scan and preview recoverable Exchange mailbox data and recover the items you need. The free version can be used to test the recovery results before deciding whether you need the full version.
https://www.nucleustechnologies.com/exchange-server-recovery.html -
1 vote
-
1 vote
-
1 vote
An error occurred while saving the comment EML to PDF is pretty simple if you only have a few emails to convert. You can open the EML file in Outlook, Thunderbird, or another email client that supports EML, click Print, and choose Save as PDF or Microsoft Print to PDF. It's free and works well for a small number of emails.
The problem starts when you have hundreds or thousands of EML files. Opening each message, printing it, naming the PDF, and repeating the process can take a lot of time. Attachments, inline images, and email formatting can also make the process more complicated.
That's where a dedicated converter can help. The MailConverterTools option mentioned above supports EML to PDF and includes features for handling attachments and duplicate emails.
Another option worth checking is Kernel Email to PDF Converter. It supports EML along with PST, OST, MBOX, MSG, and EMLX, so it can be useful if you work with different email formats. It also supports bulk conversion, which can save a lot of manual work.
I'd recommend testing any converter with a few sample emails first. Check whether the formatting, sender/recipient details, dates, images, and attachments are preserved correctly. Also check the demo or trial limits before purchasing.
For a few EML files, the free Print → PDF method is probably enough. For a large archive, dedicated software can make the whole process much faster.
Learn More: https://www.nucleustechnologies.com/email-to-pdf-converter/
-
1 vote
An error occurred while saving the comment Ah this issue i remember once i had same issue and it was really frustrating for me because it was a extremely important file to me and i couldn't able to remember the password of my PST file and i didn't wanted to mess it up with manual way so i started to find resolution online and i found Kernel PST Password Recovery and man it was a life saver for me and the BEST part it free i haven't paid a single dollar for this tool.
https://www.nucleustechnologies.com/outlook-password-recovery.html
Worth separating two things this post blends together: a migration service and a migration tool.
Apps4Rent is managed — you hire them, they run the migration. Kernel is software you run yourself, which suits teams with in-house Domino skills who'd rather keep control and avoid per-mailbox service costs.
Either way, the technical questions are the same:
Where's your data? Local NSF, Domino Server, SmartCloud Notes and HCL Verse behave differently. Domino Server files often can't be previewed first.
What's your destination? Archive mailboxes and public folders are where tools and providers often have gaps.
32-bit Notes client required? Many tools need it, and a 64-bit install blocks migration outright.
Kernel Lotus Notes to Office 365 covers local NSF, Domino Server, SmartCloud Notes and HCL Verse to primary mailboxes, archive mailboxes or public folders, with calendars, contacts, journals and tasks included. Office 365-only, and needs a 32-bit Notes client. https://www.nucleustechnologies.com/lotus-notes-to-office365.html