Organizations seeking an alternative before renewing an expensive solution
Only the features actually in use go on the list, so feasibility and the cost gap come out as a table before the renewal negotiation.
CRM Migration & Transition
A transition service that moves an existing messaging solution or free-plan setup onto a OneSignal paid plan.
- Customer Engagement
- Strategy & design
- Build & onboarding
- Managed operations
01Overview
Service overview
CRM Migration & Transition moves your existing messaging solution or free-plan environment onto a OneSignal paid plan. What carries over unchanged and what changes is established first. The migration plan, the Korean contract, and payment in won all land in one document before the cutover date.
02Who it fits
Where it fits
Development teams that built and run push sending themselves
Sending conditions scattered through the code move onto OneSignal segments and triggers, turning push into a channel marketers operate directly.
OneSignal users notified of the free-plan policy change
The features in use and the active-user scale are checked, so the choice between upgrading and staying at reduced scope is settled before the deadline.
03What we deliver
Scope of delivery
01
Transition assessment and feature mapping
The campaigns and features currently in use are listed and the OneSignal implementation of each is verified one by one. Anything that cannot be replaced surfaces before the contract, cutting the regret that follows a move.
02
Subscriber migration and parallel verification
Push subscription data and consent states are preserved through the move, and core campaigns are replanted in OneSignal as they were. Old and new environments run together for a set period, so the cutover passes without a sending gap or a break in the metrics.
03
Plan selection and contract support
The right plan and quote are calculated from the MAU forecast, and the contract and the payment are handled to Korean standards. Adoption completes without the burden of overseas payment or an English-only contract.
How the service works
Transition with verified features and consent
Verify current campaigns in the new environment, migrate subscribers and check transition conditions through parallel operation.
Map active features and campaigns
Migrate subscribers and consent
Verify in parallel and switch over
04Why this way
Points of difference
Each point lists the deliverable that backs it.
Verified against real campaigns, not a feature table
A solution comparison table is not evidence for a transition decision. A feature marked as supported and a campaign that actually runs are not the same thing. The campaigns in operation come in as a list, and the OneSignal implementation of each is confirmed scenario by scenario. Anything that cannot be replaced is written down before the contract.
Backed by
- CRM status assessment report
- Campaign design and data definition
Client work · Cooperative
Cooperative, company C — member management
Member records sat at the centre, and product, stock, and supplier management were built on the same data.
Learn moreSending keeps running through the move
Migrations fail during the move, not after it. Consent states get lost, or sending halts in cutover week. Subscriber migration and campaign rebuild finish first, then old and new environments run together while reach is compared. The old environment comes down only when nothing is off. The rollback condition is fixed before that.
Backed by
- Working campaigns and integration records
- Performance report and expansion backlog
05How to start
From first call to kickoff
Every stage ends with an agreed scope and a deliverable in your hands.
Step 01
Assess the baseline
We gather campaign history, customer data structure, and channel status, and turn them into a baseline within two weeks of kickoff.
DeliverableCRM status assessment report
Step 02
Design the scenario
We fix one or two key campaigns against the KPIs and settle the data items they require at the design stage.
DeliverableCampaign design and data definition
Step 03
Build and verify
We build the channel integrations, segments, and journeys, then confirm missends and omissions through test sends.
DeliverableWorking campaigns and integration records
Step 04
Hand over and expand
We review results with you for four weeks after handover and agree the next quarter campaigns in priority order.
DeliverablePerformance report and expansion backlog
06Contract options
Ways to work together
- Remote delivery
- Fixed price
07Service levels
Service levels
2weeks
Baseline diagnosis after kickoff
1–2campaigns
Key campaigns set against the KPI
4weeks
Results reviewed after handover
08Example engagements
Client work and example engagements
Work we took on, plus example engagements where we have no case yet.
All client workAn organization renewing an expensive contract every year for a fraction of the features
Assume an organization looking for an alternative after renewing an expensive annual contract year after year while using only part of the features.
Example approachMap every campaign actually running to fix the transition scope, then migrate with old and new environments running together.
Intended directionOperations carry forward with a cleaner cost structure and no loss of the features in use.
Cooperative, company C — member management
Members, suppliers, products, and stock all had to run inside one system.
What we doMember records sat at the centre, and product, stock, and supplier management were built on the same data.
What it leavesWhat goes out to members, and the operations behind it, come from one record.
09FAQ
Frequently asked questions
Preserving subscription tokens and consent states is the first principle of the transition design. How much carries across untouched depends on the channel and the old environment, so that is settled in the assessment stage. Actual reach after the move is compared against the old environment.
Under the OneSignal announcement, existing accounts need a paid plan for mobile push and in-app messages from October 1, 2026 once they exceed 1,000 MAU. Web push and email stay free, and IXC reviews the transition quote and plan selection with you.
OneSignal is a customer engagement platform used, by its own published figures, by one in four global app publishers. IXC supports adoption and operations in Korea for commerce, media, and gaming.
It splits into the OneSignal licence and the IXC service fee. The licence is usage-based on MAU, and the service fee is quoted per project or as a monthly subscription depending on scope. Send us an inquiry and we will follow up with a detailed quote.
We begin with campaign history, customer-data structure, and channel status. A baseline is prepared within two weeks of kickoff, then one or two key campaigns aligned with KPIs and their required data collection are finalized during design.
We review performance together for four weeks after handover. Results inform the performance report and priorities for campaigns to expand in the following quarter, recorded in an expansion backlog for the internal team.
We share the findings from the first stage, then agree scope and schedule on that basis before delivery. A finished request for proposal is not required: the current environment and the outcome you want are enough to start.
Engineering & Operations
2026-09-26 · 23 min read
Preserving customer identity, subscription states, and campaigns when changing CRM tools
CRM migration is an operational transition that carries customer identity, messaging eligibility, active campaigns, and sending responsibility into a new environment. Even while the same customer exists in both tools, only one should own each business message.
Engineering & Operations
2026-09-26 · 18 min read
Should you operate messaging with FCM or adopt a platform such as OneSignal?
Compare FCM operations and OneSignal across data, campaign changes, permissions, observability and migration responsibilities. Evaluate direct operation, a platform and a hybrid against the same scope and total cost.
Engineering & Operations
2026-09-26 · 18 min read
Why a CRM still cannot run your campaign—check events, customer attributes and identifiers first
CRM data readiness checks whether the events, attributes, identifiers and receiving states needed for campaign decisions are correctly connected to the same customer. Visible events alone do not establish current eligibility after cancellations, withdrawals or account switches.
12Related resources
Resources for this service
Guides and checklists you can use during review and kickoff.
See all resources
Guides
2026.09.04
Moving OneSignal from free to a paid plan
What to work through when a free OneSignal account reaches the paid boundary — plans, billing axes, data cleanup, and the stay-or-move call.
Guides
2026.09.05
Deciding between in-house push and a messaging tool
How far a hand-rolled FCM and APNs setup carries you, which signals mean a tool is now needed, and what actually costs money in the move.
Contact
Contact us
Tell us your current environment and target outcome, and our team will review it and reply.
Direct line
Phone lines are open weekdays 09:00–18:00
ServiceCRM Migration & Transition
Collection and use of personal information
- Purpose · Responding to and following up on this inquiry
- Items · Name, company, work email, message, visit source (first page visited, referring site domain, campaign parameters)
- Retention · 36 months from the date consent is given
You may decline; the inquiry cannot be submitted without consent.
More ways to explore