General | |
Describe the business case | |
Describe the process step by step. Per step:
• Manual or automated step ? Human in the loop ?
• Which fields are updated ? | |
Process edge case ? Examples:
• We rely on a status field, status can be reverted
• We rely on specific human input, mistakes are posible | |
Technical contact at customer | |
Technical contact has knowledge on relational data models, SQL, Python ? | |
Technical contact had Reverse ETL onboarding from Peliqan (2 hours) | |
Project start | |
Project deadline
Please allow for 4-8 weeks, depending on complexity |
Please fill the below tables for each object type that you want to sync from a source to a target, for example “Customers”, “Invoices” and “Projects” are 3 Object types.
Overall sync | Source | Target |
Platform name | ||
Object type name | ||
Primary key (unique key) | ||
Connection added in Peliqan ? | ||
Tables visible in Peliqan ? | ||
How many rows to process ? Row count > 100K ? |
Target details | |
Do inserts in target ? | |
Do updates in target ? | |
Do deletes in target ? | |
Is the target empty ? | |
If not, should checks be done in target to avoid duplicates ? | |
What field can be used to match between source and target when checking for existing target records ? | |
Is the object linked to a parent ? | |
Is the parent already in the target or should it also be synced using Peliqan’s Reverse ETL app ? | |
How many records have to be synced in total ? | |
Do you want to write the ID of the target back into a custom field in the source ? |
Example
General | |
Describe the business case | We want to keep CRM data in sync from Hubspot to Odoo because sales data is entered in Hubspot but our services team uses Odoo |
Technical contact at customer | john@acme.com |
Technical contact has knowledge on relational data models, SQL, Python ? | Yes |
Technical contact had Reverse ETL onboarding from Peliqan (2 hours) | Yes |
Project start | Jan 1st 2027 |
Project deadline
Please allow for 4-8 weeks | March 1st 2027 |
Overall sync | Source | Target |
Platform name | Hubspot | Odoo |
Object type name | Contacts | Partners |
Primary key (unique key) | id | id |
Connection added in Peliqan ? | Yes | Yes |
Tables visible in Peliqan ? | Yes | Yes |
Target details | |
Do inserts in target ? | Yes |
Do updates in target ? | Yes |
Do deletes in target ? | No |
Is the target empty ? | No |
If not, should checks be done in target to avoid duplicates ? | No, the companies present in Odoo are unrelated, the Reverse ETL app can safely add all companies from Hubspot as new entries in Odoo. |
What field can be used to match between source and target when checking for existing target records ? | VAT number, but not needed |
Is the object linked to a parent ? | Yes: Company |
Is the parent already in the target or should it also be synced using Peliqan’s Reverse ETL app ? | Also synced by Reverse ETL app |
How many records have to be synced in total ? | Around 100K |
Do you want to write the ID of the target back into a custom field in the source ? | Yes to a custom field “Odoo_id” which we added in Hubspot for Contacts. |