Faith / Migration
Plan your move from Subsplash, Tithe.ly, or Pushpay.
Moving a ministry app means checking more than the new screens. We review the records, giving setup, store accounts, and member instructions. The written plan sets the work, target dates, and responsibilities for your move.
A staged migration plan.
Step 1
Scope, design, and discovery.
We review your current platform, campuses, giving processor, member records, and sermon archive. The written plan identifies included work, needed access, target dates, and approvals.
Step 2
Build, in parallel.
We build the agreed app and website alongside your current setup where feasible. The scope confirms app-store accounts, permissions, and what the ministry needs to review.
Step 3
Data export and import.
We check the available exports for member records, giving history, groups, and sermons. The plan states what can move, what needs testing, and what must stay with the existing provider.
Step 4
App Store submission and staff training.
We handle the submissions and reviewer notes included in your plan. Apple and Google control review decisions and timing. Your team reviews content and the staff handoff.
Step 5
Launch Sunday and cutover.
We review the launch checks with your team and agree the transition. The end date for the old platform depends on its contract and the agreed migration plan.
What carries over, what doesn't.
Check available exports
- · 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)
Check separately
- · App listing, ratings, and reviews: confirm whether the existing listing can transfer
- · Giving and purchase records: confirm the source and available exports
- · Vendor analytics and any reporting included in the new plan
- · Push subscriptions: members may need to subscribe again in the new app
The migration plan must confirm available exports, account permissions, payment responsibilities, and member communication. A new app may require members to sign in or subscribe again. Adoption depends on the ministry and its members.
The concerns that come up on every migration call.
- "Will giving drop during the transition?" Giving depends on the processor setup, member communication, and the move itself. The plan identifies the giving paths to check and how members will be guided. No giving increase or recovery rate is promised.
- "What if Apple rejects our app?" Apple controls review decisions and timing. We handle the reviewer notes and resubmission work included in your plan.
- "Our older members aren't going to update." Plan clear instructions and help for members who need it. The transition period and old-platform end date depend on your agreed plan and existing provider terms. We do not promise an adoption percentage.
- "What if the service is not a fit?" The signed agreement states the commitment, notice, exportable data, transferable accounts, any code license or handoff, and the date Rehost-managed hosting and operations stop.
Related.
Catholic
Catholic parish apps
Mass schedules, groups, giving, and parish-specific member flows.
Compare
Rehost vs Subsplash
Side-by-side with the platform most migrations come from.
Faith
Multi-campus math
Three-year cost comparisons across 1, 3, 5, 10 campus configurations.
Playbook
Multi-campus operations
How LA-area multi-campus churches run on Sunday morning.
Ready to plan your migration?
Tell us which platform you use and how many campuses you run. We’ll review account access, exports, giving, and app-store requirements before agreeing the work and target dates.