01
Email inventory
We list domains, mailboxes, data, permissions and integrations. We establish archiving, backup, device and availability requirements.
Business email
Mail server deployment
We deploy business email and migrate mailboxes from your current system. We match Microsoft 365, a supported Exchange release or Postfix to company requirements. The project covers domains, accounts, message protection, backups and send-and-receive tests after cutover. Postfix handles mail transport; mailbox access, calendars and groupware require separately selected components.
Trusted by
Companies and institutions that need stable IT.
Email migration includes applications and devices
Business email is more than employee mailboxes. Website forms, accounting systems and multifunction printers also send messages. We inventory these connections, shared mailboxes, aliases, calendars and archives so that migration does not overlook services used in daily work.
Services connected to business email
Platform selection goes together with protection for accounts, messages and data. The scope depends on your current environment and intended support arrangements.
Microsoft 365
Exchange Online mailboxes, accounts, licences and collaboration.Google Workspace
Google email and collaboration as an alternative project option.Email protection
Message filtering and reducing impersonation of your company.Backup and recovery
Mailbox backup scope and tests of data recovery.ISO 27001 · TÜV NORD Polska
TÜV NORD Polska has certified Virtline’s information security management system to PN-EN ISO/IEC 27001:2023-08. The published certificate states its scope and validity.
View Virtline’s certificateBusiness email implementation process
The pilot includes users and systems that send messages. We agree the cutover date with those responsible for the domain and email service.
02
Platform and pilot
We select a supported platform and licences. We prepare accounts, DNS records and a trial migration of representative data.
03
Migration and cutover
We transfer agreed mailboxes and change mail routing and client settings. We check queues and communication from applications and devices.
04
Checks and handover
We test sending, receiving, access and recovery. Results, exceptions and support arrangements are handed over before the old environment is retired.
Practical scope
What we hand over after email deployment
We verify agreed mailboxes and communication scenarios. A successful server login does not prove that a message was delivered.
Configured domains, mailboxes, aliases and sending rules. We document applications and devices authorised to use the server.
A record of transferred data and exceptions, including items the migration tool does not support. We check agreed mailboxes, calendars and user access.
Sending and receiving tests with selected recipients, plus checks of SPF, DKIM, DMARC and filters. We record results and limitations related to providers or domain reputation. Within the agreed scope, we check TLS encryption of email connections and certificate validity. We assess support for MTA-STS and TLS-RPT reporting for the selected platform and domain.
An agreed approach to backup, recovery, quarantine and support requests. We hand over configuration documentation and identify responsibility for later changes.
Supported versions and realistic protection
Exchange Server 2016 and 2019 reached end of support on 14 October 2025. For those installations, we plan a move to a supported solution. SPF, DKIM and DMARC help verify senders, but do not stop every scam or guarantee that every message reaches the inbox.
Source
Microsoft — Exchange Server 2016 and 2019 end of support
Microsoft's official migration plan following end of support on 14 October 2025.
Open sourceQuestions about email deployment
Can we keep our current email addresses?
+
Addresses in a company-owned domain can usually be retained. Before migration, we verify DNS access, domain ownership and provider settings. Data transfer and changes to mail routing are planned separately.
Is cloud email or our own server the better choice?
+
We compare company requirements, integrations, costs and support capabilities. A local server requires updates, backups, monitoring and delivery management. Keeping email on premises does not by itself make it more secure.
Will you migrate calendars and shared mailboxes?
+
The scope depends on the source and destination systems and migration tools. We test mail, calendars, contacts, permissions and archives in the pilot. Exceptions and items needing a separate transfer are agreed before cutover.
Will sending from a website form or printer work afterwards?
+
We include specified applications and devices in the inventory. We prepare a supported authentication method and sending restrictions. The test includes an actual message and its outcome at the recipient, not merely a connection to an SMTP port.
Plan your business email migration
Tell us your current provider, mailbox count, domains and approximate data volume. Describe archives, calendars, mail-sending applications and your target date. Do not send passwords.
Discuss email deployment