Mont-Saint-Hilaire
IT services in Mont-Saint-Hilaire: moving to Microsoft 365 without stopping work
Changing email systems makes people nervous for a plain reason: everyone uses email from morning to night. A well-run migration moves in stages while the old system is still running. OKTO Solutions runs it from Trois-Rivières, about 136 km from Mont-Saint-Hilaire, with no office and no technician stationed in town.
For an SMB in Mont-Saint-Hilaire, a Microsoft 365 migration comes down to four stages: inventory and plan, a background copy of email and files, a cutover at an agreed time, then security hardening. Data is copied, not moved, and the old server stays in service until everything is validated.
Who can migrate a Mont-Saint-Hilaire business’s email and files to Microsoft 365?
OKTO Solutions offers its services to SMBs in Mont-Saint-Hilaire from its office in Trois-Rivières, about 136 km away, and runs Microsoft 365 migrations there remotely, with a visit scheduled when the engagement calls for one. The work follows four stages. First comes an inventory: mailboxes and their size, shared mailboxes, distribution lists, files to move, applications that send email, and the domain name. Next the environment is prepared, then email and documents are copied in the background while the old system stays live. The mail cutover follows at an agreed time, often in the evening, with a final copy of recent items. Last comes security: multi-factor authentication, conditional access, sharing links closed, backup switched on and tested. Up to 25 mailboxes, the projects we have observed run 2 to 4 weeks. The old server is decommissioned only after validation. OKTO has no office and no technician stationed in Mont-Saint-Hilaire.
During the copy
What does an employee notice while the mailbox is copying?
Next to nothing, which is the point. Outlook opens the way it always has. Customers get their replies and messages get filed. In the background, several years of email are being duplicated into Microsoft 365, one folder at a time. The old system goes on receiving and sending mail until the cutover happens.
That approach removes a headache: nobody has to hunt for the perfect week to shut everything down. A large mailbox takes as long as it needs and its owner never feels it. What stretches a project is the volume to move, along with in-house applications that send email. Accounting software that emails invoices, for example, has to be spotted during the inventory and reconnected at the right moment.
The cutover is the only part anyone notices. It happens at a time set with you, usually outside office hours. One last copy collects the messages that arrived in between. Workstations and phones are then configured, and our team stays available for the first few days to explain what has changed in practice.
An Outlook mailbox mid-migration: older messages arrive, the counter climbs, and the user reads her mail the whole time.
The method
In what order does a Microsoft 365 migration unfold?
Four stages, always the same ones. One rule holds them together: the old system stays in place until the new one has been validated.
- Inventory and plan. We list mailboxes and their size, shared mailboxes, distribution lists, files to move, devices in use and applications that send email. The domain name and its records are checked. The plan sets the order, the groups of employees and the cutover window.
- Preparation and copy. The Microsoft 365 environment, licences, security policies and file structure are built ahead of time. Email and documents start copying in the background. Nothing is cut off at this point.
- Cutover and first days. Mail switches over at the agreed time, often in the evening. A final copy brings across recent items, then workstations and phones are set up.
- Security and handover to operations. Multi-factor authentication, conditional access, sharing links closed, admin accounts kept separate from everyday accounts, backup switched on and tested.
The move
Email, files, accounts: what goes where?
A migration is about more than mail. Businesses leaving an email server often have a local file share as well, and both are handled in the same plan.
| What you have today | Where it goes | What gets sorted out on the way |
|---|---|---|
| Mailboxes, calendars and contacts | Exchange Online | Shared mailboxes, distribution lists and aliases carried over one by one |
| Common folders on the server or a network drive | SharePoint | Site and library structure, permissions granted by group rather than by person |
| Each employee’s working documents | OneDrive | Sharing links open to anyone found and closed |
| Employee accounts | Microsoft 365 identities | Multi-factor authentication, admin accounts distinct from everyday accounts |
If your Microsoft 365 environment already exists and nobody is really in charge of it, the full scope of what we manage is on the Microsoft 365 services page.
Three jobs in one setup: mailboxes migrate, licences are matched to real use, then Teams and SharePoint are built with access by group.
While we are at it
Why review licences and access during the migration?
Because everything is already laid out on the table. The inventory has counted mailboxes, workstations and people. Carrying over what existed as-is would mean moving the clutter along with the furniture.
Licences are picked workstation by workstation, based on what the person really does: email only, installed applications, device management, advanced security features. Not everyone needs the same subscription, and licences no longer in use are removed. Costs are presented on request, once the workstation inventory is complete.
Files follow the same idea. In SharePoint, permissions go to groups instead of individuals. When someone changes roles, that person changes groups and nobody has to dig through folders one at a time.
One point tends to be learned too late. Microsoft guarantees that its platform is available and keeps deleted items for a limited period. That is not a backup. We add one, dedicated to Exchange, SharePoint, OneDrive and Teams, with restore tests.
The ground
Mont-Saint-Hilaire, about 136 km from Trois-Rivières
Mont-Saint-Hilaire is in Montérégie, within the regional county municipality of La Vallée-du-Richelieu. For 2025, the estimate from the Institut de la statistique du Québec, still provisional, is 19,447 residents.
At that distance we publish no on-site response time, and we have neither premises nor a technician stationed in Mont-Saint-Hilaire. A migration copes well with that: a good share of the work is driven from our screens. The service is delivered remotely; travel is added when the engagement requires it.
After the cutover, the environment can move into managed IT services. There are three levels, Base, Standard and Complet, compared on our plans page. On weekdays, regular support answers from 8 a.m. to 5 p.m. The emergency line is built into the Complet plan. Other towns we cover appear on the service areas page. To tell us about the email system you run today, use the contact page.
Questions and answers
Your questions about a migration in Mont-Saint-Hilaire
How long does a Microsoft 365 migration take for a business in Mont-Saint-Hilaire?
Do we have to close the office while the mail is being copied?
Can messages or files get lost along the way?
Do we keep our email addresses and our domain name?
Does someone need to be on site in Mont-Saint-Hilaire on cutover day?
Is the migration included in a monthly plan?
Is your email still living on an old server?
Tell us how many mailboxes you have, where your files sit and which applications send email. We come back with a work sequence and a range for the duration.
Reviewed by Antonio Pazzi, president of OKTO Solutions · updated