Onboarding & trust

How implementation, data ownership and support work at Randel

Randel is implemented together with your team, not switched on as instant self-serve software. The work moves through five stages: discover how you operate today, agree a scope and quote, configure the platform, migrate data when needed and roll out to admins and members. The timeline comes from the approved scope rather than a fixed promise. Your organization owns its community data, Randel hosts and operates the platform, and support comes from people, not an AI-only channel.

By the Randel team · Last reviewed September 27, 2026

At a glance

  • Five stages: discover, scope, configure, migrate, roll out
  • Scope and quote approved before any work starts
  • Data migration available when needed
  • Client owns the data; Randel hosts and operates the platform
  • Human support included, no AI-only support
  • Email notifications live; WhatsApp notifications planned

The Randel implementation process, step by step

Implementation is where most of the value of new membership software is won or lost. A clear process keeps expectations aligned and makes sure nothing is configured before your team has agreed what it needs.

  1. 1

    Discover

    Map how you currently manage members, dues, events, meetings, documents and communication, including the spreadsheets and side tools that fill the gaps. The goal is to understand real workflows, not just a feature wish list.

  2. 2

    Scope and quote

    Agree in writing what will be configured, what data will be migrated and whether any extra development is needed. The quote is approved before work starts, and the timeline is derived from this scope.

  3. 3

    Configure

    Set up membership plans, permissions and groups, the white-label look and feel (logo, custom domain, colors), language and feature configuration, and the connection to your own Stripe account.

  4. 4

    Migrate

    When migration is part of the scope, existing member records and history are prepared, imported and checked against the source so the team can trust the new system from day one.

  5. 5

    Roll out

    Train admins, verify each workflow with real cases and move activity into the platform. Many teams move one workflow at a time, for example renewals first and events next, so members are not overwhelmed.

how Randel implementation and onboarding work →

What your team should prepare before kickoff

Implementation moves faster when the organization arrives with a few decisions already made. None of this needs to be perfect, but having it written down gives the discovery stage something concrete to work with.

Nominate one internal owner who can answer questions and make day-to-day decisions, and agree who approves the scope. Gather your current membership plans and prices, the rules for renewals and cancellations, the event types you run in a typical year and the documents members are asked to sign. Finally, note the moments in your calendar that cannot be disrupted, such as a renewal season or an annual conference, so the rollout can be planned around them.

  • One internal owner and one scope approver
  • Current plans, prices, renewal and cancellation rules
  • A year of typical events and meetings
  • Membership terms, contracts and regulations members sign
  • Busy periods the rollout should avoid

Data migration checklist before you move member records

A migration is only as good as the data going into it. Working through this checklist before the migrate stage saves rework and avoids importing old problems into a new system.

  • List every source: spreadsheets, payment exports, event tools, email lists and shared folders
  • Choose one unique identifier per member, usually an email address, and resolve duplicates
  • Agree which fields are required and which can be dropped
  • Record each member's current plan, status and renewal date
  • Separate active, lapsed and prospective members before importing
  • Collect signed documents and note which member each belongs to
  • Decide how much event and payment history is worth bringing over
  • Review consent and communication preferences with your privacy obligations in mind
  • Validate a sample of imported records against the source before going live

moving from spreadsheets to membership software →

Who owns the data: ownership vs hosting

Ownership and hosting are different questions. With Randel, the client organization owns its community data: member records, participation history, documents and operational information. Randel hosts and operates the platform that stores and processes that data on the organization's behalf.

The distinction matters for governance and for privacy law. Under frameworks such as the GDPR in Europe and the LGPD in Brazil, the organization that decides why and how member data is processed carries specific responsibilities, and service providers carry others. Review how those roles apply to your organization with your own advisers, and read Randel's security and privacy documentation as part of that review.

Randel security, privacy and compliance information →

Procurement questions to ask any membership software vendor

Whether or not you choose Randel, these questions surface the differences that sales pages tend to leave out. Ask for written answers so you can compare vendors side by side.

  • Who owns the member data, and how do we get a full copy of it?
  • What happens to our data if we end the contract?
  • Is implementation scoped and quoted before work starts, or billed open-ended?
  • Is data migration included, quoted separately or left to us?
  • How is the timeline set, and what does it depend on?
  • Is support handled by people who know our setup, or only by tickets and bots?
  • How are custom features estimated and billed?
  • Which features are live today, and which are only on the roadmap?
  • Does the vendor take a commission on member payments?

how to choose membership management software →

Human support during and after rollout

Community operators need help from people who understand membership workflows, not only a help center. Randel includes human support during implementation and afterwards, with a relationship-first approach rather than AI-only support. Demo requests usually receive a follow-up within one business day.

Be clear about what is available today. Email notifications are live, and WhatsApp notifications are planned but not yet available. The Randel website is published in English, Portuguese (Brazil) and Traditional Chinese, and the member-facing language configuration is agreed during scoping.

talk to the Randel team about your implementation →

Related questions

Can we keep our current tools running during rollout?

Yes. A phased rollout can be agreed in the scope, so existing tools keep working until each workflow has been verified in Randel. This reduces risk around renewals and upcoming events.

What if we need a feature Randel does not have yet?

Extra development is available pay-as-you-go in 8-hour blocks at US$ 360, charged for actual monthly usage, with the estimate agreed before any work starts.

Can we buy extra training for new staff later?

Yes. Consulting and training are available in 4-hour blocks at US$ 240, charged for actual monthly usage. This is useful when board members or staff change after launch.

Who on our side should be involved in discovery?

Usually the person who runs day-to-day member operations, whoever handles finance and payments, and a decision maker such as an executive director or board member who can approve the scope.

Want to see Randel for your community?

Book a demo and we usually follow up within one business day.

Book a demo