Skip to content
<Partner> Client: <Client Name>Legacy Gateway Provider: <Legacy Payment Processor>
Provide file drop form to <Partner> and/or <Partner> client for submitting files related to recurring schedule migrationGather requirements from <Partner> and/or <Partner> client for preparing the recurring schedule import filePrepare recurring schedule import file according to import template provided by <Partner>Deliver completed file to <Partner> using preferred le share methodManage communication related to recurring schedule migration between gateway providers and <Partner> client as requested by <Partner>
Project will be considered complete after tokenization is complete and the schedule file is successfully imported by the <Partner> Engineering team.Average Duration: 6-8 weeks Dependencies Client is ready to begin RSM at project Kickoff (old forms turned off, new forms turned on) Provider responsiveness: both providers are responsive and quick to provide data exports and transfers, imports, etc. A source gateway that allows card data exports. Some do not in which case recurring schedule migrations are not possible. Notes While the technical execution of the RSMs is concise, external factors frequently extend the project timeline even beyond the 8 weeks. The most common of these factors is an unresponsive source platform, gateway or payment processor
Receiving System: <CRM>Receiving Gateway Provider: <New Payment Processor>Legacy Gateway Provider: <Legacy Payment Processor>
Provide file drop form to [Client Name] for submitting files related to recurring schedule migrationGather requirements from [Client Name] and/or <CRM> for preparing the recurring schedule import filePrepare recurring schedule import file according to import template provided by [Client Name]Deliver completed file to [Client Name] using preferred file share methodManage communication related to recurring schedule migration between gateway providers and [Client Name].
Training and/or consulting in <CRM> or other software platformsPreparation of other import files not related to the recurring schedule migration (i.e., offline gift import, etc.)Data cleaning requiring the use of third-party validation services (i.e., email address verification, address standardization, etc.)File export assistance by logging into [Client Name]’s legacy systems
Project can commence 3 business days from contract execution.Project will be considered complete after tokenization is complete and the schedule file is successfully imported by the <Partner> Engineering team.Average Duration: 6-8 weeks Dependencies Client is ready to begin RSM at project Kickoff (old forms turned off, new forms turned on) Provider responsiveness: both providers are responsive and quick to provide data exports and transfers, imports, etc. A source gateway that allows card data exports. Some do not in which case recurring schedule migrations are not possible. Notes While the technical execution of the RSMs is concise, external factors frequently extend the project timeline even beyond the 8 weeks. The most common of these factors is an unresponsive source platform, gateway or payment processor
Standard Budget: 10-16 hours Breakdown 5-8 hours technical execution (depending on the data cleanliness) 5-8 hours project management This piece is the most variable especially when client or providers are not being responsive. Such delays necessitate more check-ins, context switching, etc. Notes A simple export project can be done in as little as 5 hours. However, complex import projects can take as much as 12 or more hours.
RSM: Client
Partner Paper
Executive Summary
Rooted Software is pleased to offer recurring schedule migration services as directed by <Partner>.
The Scope of Work is detailed below and applies only to the following <Partner> client and legacy
gateway provider(s):
Scope of Work
Project Timeline
Rooted Paper
Executive Summary
Rooted Software is pleased to offer recurring schedule migration services for [Client Name].
The Scope of Work is detailed below and applies only to the following [Client Name] and legacy
gateway provider(s):
Scope of Work
The following services are considered out of scope under this agreement:
Project Timeline
Project Hours
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.