Google Workspace FAQ’s

FAQ's On Google Workspace Pricing, Setup & Migration

1. How do I properly configure MX records for Google Workspace to ensure zero email loss?

To route your domain’s incoming mail to Google’s servers, you must update the Mail Exchanger (MX) records in your DNS provider’s control panel. Google Workspace requires specific destination addresses and priorities. The primary record is ASPMX.L.GOOGLE.COM with a priority of 1. It is highly recommended to lower DNS TTL (Time to Live) to 300 seconds at least 24 hours before making the switch. This ensures the new MX records propagate across global DNS servers swiftly, minimising the risk of dropped emails during the transition.

2. What is the technical difference between SPF, DKIM, and DMARC, and why are they mandatory?

These three protocols form the triad of email authentication, critical for preventing your emails from landing in recipients’ spam folders:

SPF (Sender Policy Framework): A TXT record specifying which IP addresses and domains are authorised to send email on your behalf.
DKIM (Domain Keys Identified Mail): Adds a cryptographic signature to your outgoing emails. Google Workspace generates a unique public key that administrators add to the DNS as a TXT record, alongside a private key that Google securely stores on its servers to sign outgoing mail. This cryptographic pairing ensures unauthorised parties do not tamper with the email content in transit.
DMARC (Domain-based Message Authentication, Reporting, and Conformance): Tells receiving mail servers what to do if an email fails SPF or DKIM checks (e.g., quarantine or reject the message) and sends reports back to the administrator.

3. How can we implement “Dual Delivery” or “Split Delivery” during a phased migration?

For large organisations, migrating all users at once isn’t always feasible. Google Workspace handles this through advanced routing protocols:

Split Delivery: Users are split between the legacy mail server and Google Workspace. Incoming mail hits Google’s servers first. If the user exists in Workspace, it is delivered there. If not, Google routes the message to the legacy server.
Dual Delivery: Administrators can configure the system to deliver mail to both the legacy server and the Google Workspace inbox simultaneously. They often use this method for compliance testing or as a safety net before fully decommissioning the old server.

4. Will we lose any emails during the transition?

Absolutely not. By carefully lowering DNS TTL times and using advanced routing methods before the final cutover, we ensure that every incoming email is captured either by the old server or the new Google Workspace inbox. The final delta sync guarantees nothing falls through the cracks.

5. How long does an email migration take?

The timeline depends heavily on the volume of data and the speed of the legacy server’s API. A small team might be migrated over a weekend, while an enterprise with terabytes of data might require a multi-week phased approach. We establish a clear timeline during the initial audit.

6. Will our folder structures and labels stay the same?

Yes. Whether you are coming from an Outlook environment heavily reliant on nested folders or a system using tags, our migration tools translate your existing organisational structure directly into Gmail labels.

7. Do you handle calendar and contact migration too?

Yes. In addition to mail, we migrate personal contacts, global address lists, and calendar data (including recurring events and meeting permissions) whenever supported by the source platform.

8. Do you help migrate emails from Gmail or other email providers?

Yes. Our team provides complete assistance through our Google Workspace migration service. A Google reseller can migrate emails from free Gmail, Outlook, Zoho, cPanel, or other mail servers without data loss and with minimal downtime.

9. What is the best method for migrating legacy PST files and Exchange data to Google Workspace?

For enterprise environments, the Google Workspace Migrate tool (a locally installed platform) enables administrators to migrate large volumes of data from Exchange, SharePoint, or file shares. For smaller-scale setups or individual users, the Google Workspace Migration for Microsoft Outlook (GWMMO) tool can securely import PST files directly into a user’s cloud inbox, maintaining folder hierarchies and calendar events.

10. Why should I buy Google Workspace from a reseller instead of Google directly?

Buying from a reseller gives you local expert support, help with email migration, admin configuration, GST billing, and ongoing assistance—services not included when purchasing directly from Google.

11. Can you help with admin settings?

A: We assist with admin panel configuration using our Workspace admin management services.

12. Does namaSTu.com provide technical support after purchase?

Yes. We offer ongoing help via our Workspace technical support team, including user management, security policies, troubleshooting, and Workspace optimisation.

13. Will I get GST billing if I buy Google Workspace from a reseller in India?

Yes. Indian Google Partners provide GST-compliant invoices, which help businesses with accounting and tax claims.

14. Can a reseller help secure my Google Workspace account?

Yes. Resellers assist with 2-step verification, data loss prevention (DLP), admin security policies, device management, and best practices to protect business data.

15. How much does Google Workspace cost?

A: You can view detailed Workspace plan pricing and GST billing details here.