Horizontal CRM · Sales Hub

eWay-CRM to HubSpot

Outlook- and Microsoft 365-integrated CRM covering contacts, deals, projects, tasks and marketing.

In short

eWay-CRM data can move into HubSpot, landing mainly in Sales Hub. 3 of 8 mapped objects move directly (Contacts, Companies and Tasks); 3 items need manual work and 3 do not move. Plan roughly 2-4 weeks for a small move and 8-16 weeks for a large one.

Last reviewed 2026-10-29 · Also relevant to Marketing, Service, Data hubs · 10 sources

1 · Checklist

Migration checklist for eWay-CRM

Three phases, specific to this system. Tick steps off as you go.

0 of 15 steps doneTick steps off as you go. Your progress stays in this browser.

Before

0 of 5 done

During

0 of 5 done

After

0 of 5 done
2 · Cost

What 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.

How many records?
Custom objects?
Automation to rebuild?
History to bring?

A planning aid built from the three scenarios below. It is not a quote.

The three scenarios

low complexity

Small migration

2-4 weeks

<10k records

Excel/CSV-driven.

medium complexity

Mid migration

4-8 weeks

10k-100k records

API export, association rebuild and workflows.

high complexity

Large migration

8-16 weeks

>100k records or heavy email history

Projects, activities and permissions add effort.

What moves the number

Volume of activities and emailsCustom fields and tenant-specific structureAssociation export coverageProject and timesheet remodellingWorkflow, permission and report rebuildCloud versus on-premise access effort

Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.

3 · Where to begin

Access, mapping and limits

Start with how data leaves eWay-CRM: what you need to get in, what lands in HubSpot, and what will not.

API

JSON/REST-style web service (API.svc, with Swagger and Postman docs); the older WcfService/Service.svc endpoint is deprecated

Credentials needed

Web Service URL, plus a dedicated API user (or OAuth ClientID/ClientSecret with a redirect URL).

Admin permission

The API user needs enough permissions for the objects it reads. On cloud, support must enable API help and generate OAuth clients.

Choose your route

How will you move the data?

No native connector was found.

  • You need: Web Service URL, plus a dedicated API user (or OAuth ClientID/ClientSecret with a redirect URL).
  • Permission: The API user needs enough permissions for the objects it reads. On cloud, support must enable API help and generate OAuth clients.

Native imports often bring over only some data, so check coverage per object in the mapping below.

Where each object lands

yes movespartialmanualno

In eWay-CRM

In HubSpot

Contacts
Companies
Deals
Tasks
Emails
Custom objects
Files
Select an object

Hover or tap anything on the left to see where it lands.

What to expect

Workflows and automation rules

These are configuration and must be rebuilt as HubSpot workflows.

User permissions and roles

The permission model is eWay-specific and needs rebuilding in HubSpot.

Reports and dashboards

They need rebuilding in HubSpot reporting.

4 · Governance

Data governance and compliance

Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.

0 of 5 agreed
Method

How we researched this page

How much to trust each section, and where it comes from.

InsufficientPartialVerified

The API, auth and Excel export are backed by vendor docs and repos. Object-to-HubSpot mapping, limits, residency and certifications are not documented in what I found, so those rest on category-level knowledge. No native HubSpot connector is documented.

Sources

Related migrations

Quick answers

Frequently asked questions

How do I migrate eWay-CRM to HubSpot?

1. Get the Web Service URL and create a dedicated eWay API user with read permissions. 2. Request OAuth ClientID/ClientSecret from support, or create them via the SQL stored procedure if on-premise. 3. Pull the Swagger spec and list the entities and custom fields in use. 4. Create HubSpot custom properties for ItemGUID and any eWay custom fields.

What data can move from eWay-CRM to HubSpot?

These objects move directly: Contacts, Companies and Tasks. Check the mapping table for partial and manual items.

What does not move from eWay-CRM to HubSpot?

Workflows and automation rules, User permissions and roles and Reports and dashboards. Plan to rebuild or retire these.

How long does a eWay-CRM to HubSpot migration take?

Small (<10k records): 2-4 weeks. Mid (10k-100k records): 4-8 weeks. Large (>100k records or heavy email history): 8-16 weeks. These are planning estimates, not a quote.

What access do I need to export from eWay-CRM?

Web Service URL, plus a dedicated API user (or OAuth ClientID/ClientSecret with a redirect URL). The API user needs enough permissions for the objects it reads. On cloud, support must enable API help and generate OAuth clients.

Is there a native HubSpot connector for eWay-CRM?

No native connector was found. Plan a CSV, API or third-party tool route.

What compliance issues apply when moving eWay-CRM data?

Check: Possible special-category or financial data in free-text notes and attachments. Agree consent, retention and access rules before exporting.

Talk to a partner

Moving eWay-CRM 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
Talk to a partner