{
  "slug": "vtenext",
  "url": "https://apps.sectorgrowth.com/integrations/vtenext/",
  "name": "vtenext",
  "vendor": "VTENEXT",
  "aliases": [
    "vtenext CRM",
    "vtenext CRM+",
    "VTE CRM",
    "vtenext Community Edition"
  ],
  "website": "https://www.vtenext.com/en/",
  "category": {
    "slug": "sales-and-marketing-platforms",
    "name": "Sales and marketing platforms",
    "url": "https://apps.sectorgrowth.com/categories/sales-and-marketing-platforms/"
  },
  "summary": "vtenext is an Italian open source CRM with a built-in process engine. What connecting it to HubSpot takes, inside its own synchronization and beyond it.",
  "answer": "Yes, from vtenext rather than HubSpot. The HubSpot App Marketplace lists no vtenext app as of September 2026, but vtenext's own Synchronizations settings include HubSpot for accounts, contacts, potentials, trouble tickets, targets and users. When quotes, sales orders or invoices must reach HubSpot too, we recommend one custom API integration over vtenext's REST webservice for every object, at 70 to 150 build hours.",
  "nativeApp": {
    "status": "none",
    "verifiedAt": "2026-09-28"
  },
  "api": {
    "style": "rest",
    "auth": "basic",
    "webhooks": "partial",
    "changedSince": "unknown",
    "sandbox": "unknown",
    "docsUrl": "https://usermanual.vtenext.com/books/developers/page/webservice-rest"
  },
  "objects": [
    {
      "source": "Accounts",
      "hubspot": "company",
      "direction": "two_way",
      "key": "Full vtenext record id, such as 3x310, held in a custom HubSpot property"
    },
    {
      "source": "Contacts",
      "hubspot": "contact",
      "direction": "two_way",
      "key": "Full vtenext record id, with email for the first match"
    },
    {
      "source": "Potentials",
      "hubspot": "deal",
      "direction": "to_source",
      "key": "HubSpot deal id stored on the potential, with the vtenext id written back",
      "notes": "The potential is where vtenext's own sales cycle starts."
    },
    {
      "source": "Quotes",
      "hubspot": "custom",
      "direction": "to_hubspot",
      "key": "vtenext quote id, associated to the deal through its potential"
    },
    {
      "source": "Sales orders",
      "hubspot": "custom",
      "direction": "to_hubspot",
      "key": "vtenext sales order id, associated to the deal and the company"
    },
    {
      "source": "Invoices",
      "hubspot": "custom",
      "direction": "to_hubspot",
      "key": "vtenext invoice id, associated to the company",
      "notes": "Head office stays the only place an invoice is edited."
    }
  ],
  "approaches": [
    {
      "kind": "custom",
      "fit": "recommended",
      "why": "vtenext's REST webservice creates, updates, retrieves and queries every module with a user's access key, and a REST hook or a process step can call the service when a record changes, so one keyed service can carry the whole cycle from potential to invoice."
    },
    {
      "kind": "ipaas",
      "fit": "possible",
      "why": "vtenext documents how to build a private Zapier integration against its REST webservice, with REST hook triggers, which suits a single flow such as new leads raising a HubSpot task at low volume."
    },
    {
      "kind": "native",
      "fit": "avoid",
      "why": "There is no vtenext app in the HubSpot App Marketplace to install. The HubSpot synchronization vtenext ships lives in vtenext's own settings, and it covers six modules with no quotes, orders or invoices."
    }
  ],
  "connectionMethods": [
    "api",
    "ipaas"
  ],
  "effort": {
    "discoveryHours": [
      10,
      20
    ],
    "buildHours": [
      70,
      150
    ],
    "buildBand": "70 to 150 hours",
    "typicalElapsed": "4 to 8 weeks"
  },
  "pattern": "webhook-queue",
  "faqs": [
    {
      "q": "Does vtenext have its own HubSpot integration?",
      "a": "Yes. vtenext's user manual lists HubSpot among the platforms in its Synchronizations settings, with accounts, contacts, potentials, trouble tickets, targets and users as the modules it can synchronize. It runs on vtenext's scheduler, every minute by default, and the manual notes that deletions made in HubSpot are not carried into vtenext. The manual does not say which vtenext licences include it."
    },
    {
      "q": "How does an integration authenticate to the vtenext REST webservice?",
      "a": "With HTTP Basic authentication on POST requests: the user name and that user's webservice access key, Base64 encoded, rather than the login password. Access keys live in the user's preferences, and the CRM's settings show which modules a given user can reach. We ask for a dedicated integration user, so the connection never depends on an employee's account."
    },
    {
      "q": "Can vtenext notify an external system when a record changes?",
      "a": "Partly. vtenext documents a REST hook subscription, set up for its Zapier integration, that posts to a URL when a record is created in a chosen module or a process condition is met, and its process engine can call a configured external web service from a process step. There is no general change feed, so we pair either one with a nightly query that reconciles counts."
    },
    {
      "q": "Is the vtenext documentation available in English?",
      "a": "Yes. vtenext publishes its user manual, including the REST webservice settings and the synchronization settings, and its developer pages on the webservice methods and the SDK in English as well as Italian, on its own manual site. A few older SDK pages exist only in Italian, but the pages an integration relies on have English versions."
    },
    {
      "q": "How does a vtenext record id work in an integration?",
      "a": "vtenext writes every id as a module prefix and a record number joined by an x, such as 3x310, and the webservice methods take that whole string. The prefix for each module comes from the describe method, where it is called idPrefix. We store the full id in a custom HubSpot property, never the number alone, because two modules can hold records with the same number."
    },
    {
      "q": "Should vtenext's HubSpot synchronization and a custom integration run together?",
      "a": "Not on the same objects. Two mechanisms writing HubSpot companies or contacts will each create records by their own matching, and the duplicates land in HubSpot. When quotes, orders and invoices justify a custom service, we let it own every object and switch the built-in synchronization off for those modules, so each record has one key and one owner."
    },
    {
      "q": "What does a vtenext and HubSpot integration take in hours?",
      "a": "Budget 10 to 20 hours of discovery and 70 to 150 hours of build for accounts, contacts, potentials, quotes, sales orders and invoices, with event intake, keyed upserts and a nightly reconciliation. If vtenext's own synchronization already covers what you need, configuring it is a small fraction of that, and we say so in discovery."
    }
  ],
  "sections": [
    {
      "depth": 2,
      "text": "Why teams connect vtenext to HubSpot",
      "anchor": "#why-teams-connect-vtenext-to-hubspot",
      "url": "https://apps.sectorgrowth.com/integrations/vtenext/#why-teams-connect-vtenext-to-hubspot"
    },
    {
      "depth": 2,
      "text": "What syncs",
      "anchor": "#what-syncs",
      "url": "https://apps.sectorgrowth.com/integrations/vtenext/#what-syncs"
    },
    {
      "depth": 2,
      "text": "Architecture",
      "anchor": "#architecture",
      "url": "https://apps.sectorgrowth.com/integrations/vtenext/#architecture"
    },
    {
      "depth": 2,
      "text": "Three ways to connect",
      "anchor": "#three-ways-to-connect",
      "url": "https://apps.sectorgrowth.com/integrations/vtenext/#three-ways-to-connect"
    },
    {
      "depth": 2,
      "text": "What breaks and how we prevent it",
      "anchor": "#what-breaks-and-how-we-prevent-it",
      "url": "https://apps.sectorgrowth.com/integrations/vtenext/#what-breaks-and-how-we-prevent-it"
    },
    {
      "depth": 3,
      "text": "Two syncs writing one company",
      "anchor": "#two-syncs-writing-one-company",
      "url": "https://apps.sectorgrowth.com/integrations/vtenext/#two-syncs-writing-one-company"
    },
    {
      "depth": 3,
      "text": "Ids that lose their module prefix",
      "anchor": "#ids-that-lose-their-module-prefix",
      "url": "https://apps.sectorgrowth.com/integrations/vtenext/#ids-that-lose-their-module-prefix"
    },
    {
      "depth": 3,
      "text": "Access keys tied to one employee",
      "anchor": "#access-keys-tied-to-one-employee",
      "url": "https://apps.sectorgrowth.com/integrations/vtenext/#access-keys-tied-to-one-employee"
    },
    {
      "depth": 3,
      "text": "Deletions that never cross over",
      "anchor": "#deletions-that-never-cross-over",
      "url": "https://apps.sectorgrowth.com/integrations/vtenext/#deletions-that-never-cross-over"
    },
    {
      "depth": 2,
      "text": "Our approach",
      "anchor": "#our-approach",
      "url": "https://apps.sectorgrowth.com/integrations/vtenext/#our-approach"
    }
  ],
  "caseStudies": [],
  "guides": [
    "https://apps.sectorgrowth.com/guides/migration-or-integration/",
    "https://apps.sectorgrowth.com/guides/choose-a-hubspot-integration-approach/"
  ],
  "status": "published",
  "verifiedAt": "2026-09-28",
  "updatedAt": "2026-09-28",
  "authors": [
    {
      "name": "Prash",
      "role": "Lead of Technical Integrations and AI Solutions"
    }
  ],
  "sources": [
    {
      "title": "Webservice REST",
      "url": "https://usermanual.vtenext.com/books/developers/page/webservice-rest"
    },
    {
      "title": "REST Webservice Methods",
      "url": "https://usermanual.vtenext.com/books/developers/page/rest-webservice-methods"
    },
    {
      "title": "18.10 REST Webservice",
      "url": "https://usermanual.vtenext.com/books/user-manual-vtenext-2607/page/1810-rest-webservice"
    },
    {
      "title": "15.4 Synchronizations",
      "url": "https://usermanual.vtenext.com/books/user-manual-vtenext-2607/page/154-synchronizations"
    },
    {
      "title": "New integration",
      "url": "https://usermanual.vtenext.com/books/creation-of-external-apps/page/new-integration"
    },
    {
      "title": "9 Sales: from the potentials to invoice",
      "url": "https://usermanual.vtenext.com/books/user-manual-vtenext-2607/page/9-sales-from-the-potentials-to-invoice"
    },
    {
      "title": "3.1.2 Lead conversion",
      "url": "https://usermanual.vtenext.com/books/user-manual-vtenext-2607/page/312-lead-conversion"
    },
    {
      "title": "17.16 Data Import",
      "url": "https://usermanual.vtenext.com/books/user-manual-vtenext-2607/page/1716-data-import"
    },
    {
      "title": "vtenext, much more than a CRM",
      "url": "https://www.vtenext.com/en/about-us/"
    },
    {
      "title": "vtenext: the European Open Source CRM",
      "url": "https://www.vtenext.com/en/"
    }
  ]
}