Use this link to share with your colleagues:
Migrating your Data: https://help.pm.leapevent.tech/a/1253665
The duration of your data migration is significantly dependent on the complexity of your data. The main considerations will be how much data you've provided, how closely it aligns with the PatronManager structure, and how many different sources it comes from.
The bulk of the work will be on our end during the data migration; however, we may reach out to you for clarification as items come up during the process. This article provides an overview of our internal process:
Data Submission Review
Before we import your data, we'll review your full submission and create a mapping guide, detailing which objects and fields each column of data will be mapped to during the data migration. This mapping guide will be made available upon request at the end of your data migration.
As we review you're data, we'll make sure that our basic criteria are met:
- One patron is listed per contact record
- Every patron has a last name (required)
- All email addresses are in a valid format
- Street addresses are normalized into Proper-case format
- Zip codes are correctly formatted, particularly those with leading zeros
- Account names are normalized into Proper-case format
If any discrepancies are discovered during the Data Submission Review, your Implementation Manager may request an additional export of data to correct any export errors.
What will happen during the data transfer?
The data migration will follow a standard sequence, starting with the largest (or most reliable) database that you've specified with your Implementation Manager:
- Account & Contact Import
- Donation Import
- Membership Import
- Ticket History Import
Depending on the complexity of your data, this process may take several weeks from your submission date. Once all files have been migrated into the system, your Implementation Manager will schedule a follow-up call to walk through the database and discuss any remaining clean-up items that will need to be taken care of post-import.
What should I do with any new data that comes into our previous system while you're transferring the data we've already submitted?
Your Implementation Manager has set aside time at the end of your implementation to process a last batch of files, which we've coined as "gap data," or the new transactions or modifications to records that have occurred since you submitted your data for migration. You can read more on this in this article.