Teams whose sales live in HubSpot or Salesforce and whose onboarding, delivery or account work happens after the deal closes, often in spreadsheets, by people who don't need a CRM seat.
Import contacts, companies and deals — and push new contacts back into the CRM.
Import accounts, contacts and opportunities, and create a Salesforce contact from an automation.
The import brings each Salesforce object in as its own table, with the account named rather than linked. Import all three, then turn the account names into links, and the structure comes back.
You'll know it worked: Open one account and compare its contacts and opportunities with the same account in Salesforce. Accounts that share a name are the ones to check by hand.
Capture the lead in RowFold, from a form or a quick record on a phone, and let an automation create the contact in the CRM once it is worth having there.
You'll know it worked: Qualify a test lead and check a contact appears in the CRM and its id in CRM id. Then change the lead's status and back again, and check no second contact appears.
The work after a deal closes doesn't fit the CRM. Onboarding steps, installs and renewals end up in a spreadsheet that copies the customer's name and loses track of which deal it came from.
Import the CRM's companies, contacts and deals as tables, then build the delivery work on tables of your own that link to them. Each project points at its deal, and each deal shows its projects.
In Salesforce, contacts and opportunities belong to accounts. The import brings each account across as a name, so which contact belongs where becomes a matter of matching text.
Convert to Relation… turns each imported Account column into a real link to the imported accounts, matching by name. Contacts and opportunities then sit under their accounts again.
People who find leads outside the CRM retype them into it, or don't. A contact met at an event lives in somebody's notebook for a week.
An automation can create the contact in HubSpot or Salesforce the moment the record exists in RowFold, and save the new contact's id back onto the record, so a second contact is never made by accident.
No. Imports only read, so importing can't edit or delete a CRM record. The only writes are the ones you put in an automation: create a contact in HubSpot, or create a contact in Salesforce. Each writes one new contact and hands back its id, which you can save on the record that caused it.
They can. Importing again updates the tables the first import made, matched on the CRM's own record IDs, and Keep in sync does that hourly or daily; an import never writes back. The CRM's values win on the columns the import fills, so a note typed into one of those is replaced on the next run, while columns you add are never touched. Delivery work still belongs on tables of your own that link to the imported ones, and those links survive every run.
A last name, which is the one field Salesforce insists on; first name and email are optional. The contact is created in the Salesforce org whose user connected RowFold, with that user's permissions. Set Save the result to a Text field and the new contact's Salesforce id is written onto the record, ready for a duplicate check.
Save the new contact's id onto the record with Save the result to, and give the automation a condition that the field is empty. The first run fills it, so any later run for that record stops at the condition. Neither CRM refuses a duplicate on its own, so this check is the one that counts.
Whichever the sales team treats as the truth. Import from that one, so every project points at the deals people actually work, and create new contacts back in it. The HubSpot page covers HubSpot's side in more detail, including what its import brings and how often to run it.
There is no template to wait for. Type a sentence about what you run and RowFold assembles the tables, links, views and dashboard around it — then you change whatever does not fit.