SQL-based selection
Use a view or query that returns only the records and fields that should be synchronized.
Database → Google Contacts → phone
We move data.We connect contacts.
DB2Google transfers selected customers, employees or suppliers from Microsoft SQL Server to Google Contacts. Your team receives current phone numbers and email addresses without repetitive manual exports.
- Automated runs
- Configurable field mapping
- Google OAuth authorization
One data sourceContacts originate in the company database
Less manual workNo repeated CSV exports
Available on phonesThrough Google Contacts synchronization
Why DB2Google
The correct data is in your database. Your people need it where they work.
The solution creates a repeatable flow between the database and the user address book. The exact scope is configured for your data structure, account count and operating rules.
Contact mapping
Name, company, phones, email, address and notes are mapped to matching Google Contacts fields.
Scheduled updates
Synchronization can run on a schedule and log new, changed and failed records.
Multiple target accounts
The deployment can be designed for one account, a team or a Google Workspace environment.
Controlled authorization
Contact access uses Google OAuth rather than storing user passwords.
Tailored deployment
Database connection, transformation rules and operating mode are adapted to your infrastructure.
Data flow
From an SQL query to a current contact
01
Source
Select tables, a view or an SQL query and define filtering rules.
02
Transform
Clean, combine and map fields to the target contact structure.
03
Authorize
The target account or Workspace environment grants the required permissions.
04
Synchronize
Changes are transferred, logged and made available on the phone.
Example mappingMicrosoft SQL Server → Google Contacts
Customer.FullName
→
Name
Customer.Company
→
Organization
Customer.Mobile
→
Phone number
Customer.Email
→
Email address
Typical scenarios
Where synchronized contacts create value
Sales teams
Customer contacts from CRM or ERP directly in the salesperson’s mobile address book.
Service and field teams
Sites, responsible people and emergency numbers available away from the office.
Internal directory
Employee contacts controlled from an HR or central database.
Suppliers and partners
Centrally managed external contacts for selected groups of company users.
Security and operations
Controlled transfer without sharing passwords
The architecture depends on the installation model. The design should limit database access, use Google authorization and retain operational logs only as required.
- Access limited to selected data
- Google OAuth instead of user passwords
- Encrypted network communication
- Result and error logging
- Test run before production
Transparent pricing
Annual licence based on target account count
The licence price is based on the number of Google accounts receiving synchronized contacts. Contact record count is not licensed; technical service limits still apply.
Starter
1 Google account
290 €/ year
- 1 production installation
- 1 Microsoft SQL Server source
- Updates during the licence term
- Email support
Team
2–10 Google accounts
590 €/ year
- 1 production installation
- 1 Microsoft SQL Server source
- Updates during the licence term
- Email support
Business
11–50 Google accounts
990 €/ year
- 1 production installation
- 1 Microsoft SQL Server source
- Updates during the licence term
- Email support
Enterprise
51+ Google accounts
custom quote
- 1 production installation
- 1 Microsoft SQL Server source
- Updates during the licence term
- Email support
Standard deployment
One-time fee from €390. Includes one MS SQL source connection, basic field mapping, configuration and a verification run.
Work outside the standard scope: €90 / hour.
Prices exclude VAT. DB2Google is offered to businesses and professional organisations (B2B). Licensing policy →
Frequently asked questions
What we need to confirm before quoting
Is DB2Google intended for IBM Db2?
No. The name means “Database to Google”. The offered scenario focuses on Microsoft SQL Server and Google Contacts.
Is synchronization bidirectional?
The default scenario is controlled transfer from MS SQL to Google Contacts. Reverse changes or deletion rules must be designed and confirmed for the specific deployment.
How many accounts can be served?
The scope may range from one account to multiple users. Google Workspace deployments require verification of the administrative and permission model.
How is pricing determined?
Pricing depends on the data model, number of accounts, mapping, synchronization frequency, installation method and required support.
What should an inquiry include?
Provide the database source, approximate contact count, target accounts, required fields and update frequency.
Non-binding inquiry
Describe the required contact flow
Send the basic parameters. They allow us to prepare focused questions and propose the next step.
- Source database and record count
- Number of target Google accounts
- Fields and update rules
- Required synchronization interval