Faith / Migration
Migrating from Subsplash, Tithe.ly, or Pushpay — without breaking Sunday.
The single biggest concern most ministry leaders have isn't the new platform — it's whether the migration breaks something on Sunday morning. This page walks through how the 30-day migration actually runs, what gets exported, what transfers, and what stays operational the whole way through.
The 30-day migration plan.
Days 1–7
Scope, design, and discovery.
First call covers your current platform setup — Subsplash, Tithe.ly, Pushpay configuration; campus count; giving processor; member count; sermon archive depth. By end of week one we have the per-campus configuration documented and the design direction approved. Your existing platform stays running the whole time.
Days 8–14
Build, in parallel.
We build the Rehost app and supporting website in parallel with your live platform. Your sermons, your branding, your service times, your campus structure — replicated and customized. We also create the App Store and Google Play developer accounts in your church's name (if you don't already have them) — these accounts stay yours forever.
Days 15–21
Data export and import.
We pull your member data, giving history, group structure, and sermon archive from the existing platform. Subsplash exports come through their export tool. Tithe.ly and Pushpay both have data-export APIs we use. Member identifiers carry over so your regulars don't lose their giving history. App Store reviews and ratings are tied to the listing, not the account, so a fresh app launch starts at zero — that's the one piece nobody can transfer.
Days 22–28
App Store submission and staff training.
We submit to Apple App Store and Google Play. Apple usually approves within 2–3 days; we handle any reviewer notes. Meanwhile your staff is briefed on the new operating model — which is mostly "you message us instead of logging into something." Most teams find it requires less training than they expected because there's no CMS to learn.
Days 29–30
Launch Sunday and cutover.
Sunday morning launch announcement from the pulpit, with a QR code that takes members to the new app on the right App Store. Old platform stays live for one more month so members who don't update right away aren't stranded. By day 60, the old platform is sunset and the bill stops.
What carries over, what doesn't.
Carries over
- · Member directory and contact information
- · Recurring giving history and giver records
- · Group structure and small-group rosters
- · Sermon archive (audio and video)
- · Event history and recurring schedule rules
- · Custom branding, colors, and content
- · Giving processor relationship (if it's already in your name)
Doesn't carry over
- · App Store reviews and ratings (tied to the old listing, not the account)
- · In-app purchase history (your giving processor has the canonical record)
- · Vendor-specific analytics dashboards (we replace with our own)
- · Push notification subscriber list — members re-subscribe via the new app (typically 80%+ within 2 weeks)
The push notification re-subscription is the only piece that takes some active member outreach. Most churches handle it with one Sunday announcement and a follow-up email; recovery is usually 80%+ within two weeks.
The concerns that come up on every migration call.
- "Will giving drop during the transition?" Brief dip in week 1–2 (5–10% reduction in digital giving) as members adjust. Recovers by week 3 and typically settles 8–15% above pre-migration levels by month 3 because the new app has a better giving flow and lower friction.
- "What if Apple rejects our app?" Apple rejection is normal for first submissions. We handle every reviewer note and resubmission cycle — that's part of the engagement. Apple typically clears faith apps within 2–4 days and rarely raises substantive issues for ministries with established member bases.
- "Our older members aren't going to update." The old platform stays live for the first month after launch, giving everyone time. We've never had a migration where the older-member adoption rate fell below 70% within 60 days, and most churches see 85%+ adoption when the senior pastor announces it from the pulpit.
- "What if we hate it after 60 days?" Month-to-month, no clawback. We hand off the data, the App Store account (which is already in your name), and the giving processor relationship. The platform shuts off; the operation keeps running. We've never had a faith client cancel after launch — but the structural option is there.