GEDYS IntraWare to HubSpot
Modular, no-code CRM/CXM platform for sales, marketing and service. It is offered as an on-premise client, a web CRM or a cloud service, and has Lotus Notes and Outlook heritage.
GEDYS IntraWare data can move into HubSpot, landing mainly in Sales Hub. 0 of 6 mapped objects move directly; 4 items need manual work and 3 do not move. Plan roughly 4-6 weeks for a small move and 14-26 weeks for a large one.
Migration checklist for GEDYS IntraWare
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
<25k records
Core objects only.
Mid migration
25k-250k records
Includes activities and pipelines.
Large migration
>250k records
Heavy customisation and multiple business units.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves GEDYS IntraWare: what you need to get in, what lands in HubSpot, and what will not.
Choose your route
How will you move the data?
No native connector was found.
- You need: To confirm
- Permission: To confirm
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
Limits: To confirm
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 14-26 weeks, usually phased.
Talk to a partnerWhere each object lands
In GEDYS IntraWare
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Contacts / persons | Contacts | partial | The vendor describes a contact database with tag-cloud attributes. The export path and field model are unverified. |
| Accounts / companies | Companies | partial | The product uses a file-structure (Akte) model for customers. The export format is unverified. |
| Opportunities / deals | Deals | partial | Sales covers lead qualification through to orders. Pipeline and stage export is unverified. |
| Activities (calendar, tasks, emails) | Tasks | manual | Activity and association export coverage must be audited. Notes, Calls, Emails and Meetings may map, but this is unverified. |
| Service requests / complaints | Tickets | partial | The vendor describes integrated service management for inquiries and complaints. |
| Projects and resource planning | Custom objects | manual | Projects, Gantt data and utilisation have no native HubSpot equivalent. |
What to expect
Logic is platform-specific and has to be rebuilt as HubSpot workflows.
Must be redesigned using HubSpot users, teams and permission sets.
Must be rebuilt in HubSpot reporting.
This is the analyst's scope focus and none of it transfers automatically.
Whether activity history and links between records can be exported is undocumented.
Owners must be matched to HubSpot users, and stages must be mapped.
The no-code platform lets customers build their own applications, so schemas vary by customer.
Ask the vendor or partner for a full database or API export spec before scoping.
Run a schema inventory and a pilot import.
Confirm the deployment type early.
Test the export on a sample set and reconcile counts.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
The product is active and its category is documented by third-party sources. I found no vendor API or export documentation and no HubSpot connector documentation, so access and object mapping rest on category-level knowledge.
Sources
Related migrations
Frequently asked questions
How do I migrate GEDYS IntraWare to HubSpot?
1. Confirm the deployment type (on-premise client, web or cloud) and version, for example release 8.x. 2. Request the export and API documentation from GEDYS or the implementation partner. 3. Inventory the Akte structures, custom no-code applications and fields. 4. List the owners, teams, roles and permissions to recreate.
What does not move from GEDYS IntraWare to HubSpot?
Automation and workflow logic built in the no-code platform, Permissions and role model and Dashboards and reports. Plan to rebuild or retire these.
How long does a GEDYS IntraWare to HubSpot migration take?
Small (<25k records): 4-6 weeks. Mid (25k-250k records): 8-14 weeks. Large (>250k records): 14-26 weeks. These are planning estimates, not a quote.
What compliance issues apply when moving GEDYS IntraWare data?
Check: Customers include automotive and financial-sector firms, so financial data may be present. Agree consent, retention and access rules before exporting.
Moving GEDYS IntraWare into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner