Accounts and contacts
The two writable objects, with no delete mode.
Sync PostgreSQL to Front with Polytomic so accounts and contacts carry context from your own database. Reverse ETL discovers existing Front custom fields, merges them on update, and throttles itself to eighty percent of Front's published rate limit.
The two writable objects, with no delete mode.
Updates preserve the fields you did not map.
Reads Front's own rate limit header and stays under it.
Polytomic is bi-directional by default, so you can move data the other way just as easily.

Jonathan Krangel
VP Global Head of Revenue Operations
“Polytomic handles so many ETL and sync jobs at Cursor. They are a true partner to us.”
Follow these simple steps to connect PostgreSQL with Front in minutes
Connect PostgreSQL
Connect Front
Create sync
Enable sync
Connect PostgreSQL to Polytomic with host, port, database, and credentials.
Connect Front to Polytomic with an API token from your Front account.
Sync data in either direction between PostgreSQL and Front. Choose the source data and destination objects for the direction you need.
Map the fields, choose the sync schedule and behavior, then save and enable the sync.
Get answers to common questions about the integration process
Sync data in either direction between PostgreSQL and Front.
Use both integrations' source and destination capabilities in one managed sync workflow.
Enterprise encryption and security protocols ensure your data remains protected.
Get up and running in minutes with our step-by-step integration guide.