Migrate your Oncord data
Website-builder-first all-in-one platform combining contact management, email/SMS marketing, and e-commerce with bundled hosting. Ideal for SMBs who want one vendor for their entire web presence.
In its favor
Why people choose Oncord
The signal that keeps Oncord on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
All-in-one consolidation of website, contact database, email, SMS, and commerce eliminates paying separate vendors for each function, which is the most cited reason customers switch to Oncord.
Unlimited contacts on the base plan means small businesses never hit a per-record ceiling, unlike CRMs that bill per contact or per seat.
Bundled web hosting with SSL, automatic backups, and platform updates removes the need to manage a separate hosting account or worry about security patches.
Integrated drag-and-drop website editor with pre-built CRM and marketing tools lets non-technical users build a complete online presence without touching code.
Integrations with Xero, MYOB, Cliniko, and simPRO connect the contact database directly to accounting and field-service workflows used by Australian small businesses.
Feature depth creates a steep learning curve — customers report feeling overwhelmed by the number of tools available and not knowing where to start.
Built-in analytics are described as shallow compared to Google Analytics or dedicated BI tools, frustrating customers who need detailed campaign reporting.
No formal data export process means customers leaving Oncord must manually download backups or build custom exports, adding friction to migration timelines.
Analytics limitations and the learning curve combine to create churn among customers who expected a simpler, more intuitive experience out of the box.
The platform is website-builder-first rather than CRM-first, which causes friction for teams that prioritised contact management over web presence.
Reasons to switch
Why people leave Oncord
The recurring reasons buyers give for replacing Oncord. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Oncord fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Oncord pricing overview
Oncord uses a modular pricing model: the base plan at $39/month covers website hosting and the contact database. Marketing and Commerce are separate $40/month add-ons. Email accounts are billed separately at $5 per account per 15GB. Lite plans at $5/month cover one module only with significant feature restrictions. Enterprise starts at $2,000/month with SLA and priority support.
Base (Website + Contacts)
Tier 1 of 5
$39/month
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Oncord's schedule — see our quote-based pricing →
What gets migrated
Oncord object support
Object-by-object support for Oncord migrations. Per-pair details surface during scoping.
Contacts
Fully supportedContacts are the primary CRM object in Oncord. The platform advertises unlimited contacts on base plans. We map Contacts 1:1 into the destination CRM's contact object, preserving all standard fields and any custom field values. The activity feed (interaction history) is also extracted and linked to the contact record where the target schema supports it.
Groups
Fully supportedGroups function as static tagging and segmentation lists in Oncord. We export all Groups and map them to the destination's equivalent segment or tag structure. On Lite plans, filters are restricted to Groups only, which is important to note for customers migrating away from restricted-tier accounts.
Custom Fields
Fully supportedOncord exposes CustomFields via its internal API component. We can read, write, and map custom field definitions and values. We handle type mapping (text, number, date, dropdown) between Oncord's schema and the destination's field types. The CustomFields API reference is available at /developer/api/components/settings/customfields/.
Products (Commerce)
Mapping requiredProducts are only available when the Commerce add-on ($40/month) is active. We export product name, description, price, SKU, inventory, images, and any custom product fields. Commerce gating must be confirmed during scoping — if the customer never purchased the Commerce module, no product data exists to migrate.
Events
Mapping requiredEvents are part of the Marketing module and include RSVP functionality. We export event name, date, location, capacity, and attendee list (linked to Contacts). Mapping to the destination's event or calendar object depends on the target platform's event schema, which may require custom field work for registration-specific data.
Automation Workflows
Mapping requiredMarketing automation workflows trigger on contact activity, group membership, or time-based schedules. We document the workflow structure (triggers, conditions, actions) but migration of the automation logic itself is complex because workflow engines vary significantly between platforms. We export workflow definitions as configuration records and flag which automations need manual recreation.
Users / Administrators
Mapping requiredOncord includes unlimited admin users on base plans. We export user records including name, email, and role. Owner assignment on Contacts maps to the destination's user record, but role semantics differ between platforms so explicit mapping is required.
Web Forms
Mapping requiredWeb forms grow the contact database and can carry custom field mappings per form. We export form definitions and their field-to-contact-property mappings so the destination's equivalent form builder can replicate the same data-capture structure.
Discounts and Coupons
Mapping requiredAvailable only with the Commerce add-on. We export discount rules, coupon codes, eligibility conditions, and usage limits. Mapping to destination promo objects depends on whether the target platform has equivalent discount mechanics.
| Object | Support | Notes |
|---|---|---|
| Contacts | Fully supported | Contacts are the primary CRM object in Oncord. The platform advertises unlimited contacts on base plans. We map Contacts 1:1 into the destination CRM's contact object, preserving all standard fields and any custom field values. The activity feed (interaction history) is also extracted and linked to the contact record where the target schema supports it. |
| Groups | Fully supported | Groups function as static tagging and segmentation lists in Oncord. We export all Groups and map them to the destination's equivalent segment or tag structure. On Lite plans, filters are restricted to Groups only, which is important to note for customers migrating away from restricted-tier accounts. |
| Custom Fields | Fully supported | Oncord exposes CustomFields via its internal API component. We can read, write, and map custom field definitions and values. We handle type mapping (text, number, date, dropdown) between Oncord's schema and the destination's field types. The CustomFields API reference is available at /developer/api/components/settings/customfields/. |
| Products (Commerce) | Mapping required | Products are only available when the Commerce add-on ($40/month) is active. We export product name, description, price, SKU, inventory, images, and any custom product fields. Commerce gating must be confirmed during scoping — if the customer never purchased the Commerce module, no product data exists to migrate. |
| Events | Mapping required | Events are part of the Marketing module and include RSVP functionality. We export event name, date, location, capacity, and attendee list (linked to Contacts). Mapping to the destination's event or calendar object depends on the target platform's event schema, which may require custom field work for registration-specific data. |
| Automation Workflows | Mapping required | Marketing automation workflows trigger on contact activity, group membership, or time-based schedules. We document the workflow structure (triggers, conditions, actions) but migration of the automation logic itself is complex because workflow engines vary significantly between platforms. We export workflow definitions as configuration records and flag which automations need manual recreation. |
| Users / Administrators | Mapping required | Oncord includes unlimited admin users on base plans. We export user records including name, email, and role. Owner assignment on Contacts maps to the destination's user record, but role semantics differ between platforms so explicit mapping is required. |
| Web Forms | Mapping required | Web forms grow the contact database and can carry custom field mappings per form. We export form definitions and their field-to-contact-property mappings so the destination's equivalent form builder can replicate the same data-capture structure. |
| Discounts and Coupons | Mapping required | Available only with the Commerce add-on. We export discount rules, coupon codes, eligibility conditions, and usage limits. Mapping to destination promo objects depends on whether the target platform has equivalent discount mechanics. |
Gotchas
What to watch for in Oncord migrations
Issues we've hit on past Oncord migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Email accounts are not included in the base subscription
Lite plan restrictions gate most CRM and marketing data
No formal export or migration tooling exists
Commerce and Marketing are optional paid add-ons
| Severity | Issue |
|---|---|
| Medium | Email accounts are not included in the base subscription |
| Medium | Lite plan restrictions gate most CRM and marketing data |
| High | No formal export or migration tooling exists |
| Low | Commerce and Marketing are optional paid add-ons |
Leaving Oncord?
Where Oncord customers move next
12 destinations Oncord can migrate to.
How a Oncord migration works
Four steps, Oncord-specific
Connect
Not publicly documented into Oncord. Scopes limited to read-only on the data we move.
Map
We translate Oncord-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Oncord quirks before production.
Migrate
Full migration with Oncord rate-limit handling. Rollback available throughout.
FAQ
Oncord migration FAQ
Answers to the questions buyers ask most during Oncord migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Oncord migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Oncord.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Oncord setup and destination — written quote back within a business day.