> For the complete documentation index, see [llms.txt](https://solutions.fundraisingbox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://solutions.fundraisingbox.com/knowledge-base/initial-data-mapping-and-synchronization.md). # Initial Data Mapping & Synchronization The initial data mapping and synchronization is a one-time setup process that maps existing records between FundraisingBox and the CRM system. It ensures the connector can identify corresponding objects on both sides. {% hint style="info" %} The initial step does not harmonize data between the systems; it only establishes fixed relationships as the foundation for subsequent automated synchronization. {% endhint %} ### Scenarios and Approach {% hint style="warning" %} The initial data synchronization is critical for ensuring a smooth integration. If Scenario 3 or 4 applies to your project, it is mandatory to carry this out. Otherwise, a go-live will not be possible. {% endhint %} #### Scenario 1: No Data in FundraisingBox In this case, no initial mapping is required. Once the integration is activated, data will be automatically synchronized from FundraisingBox to the CRM system according to the defined mapping. #### Scenario 2: Small to Medium Data Volumes Existing Only in FundraisingBox For small to medium volumes of donations (up to approx. 50,000 records/transactions) that exist exclusively in FundraisingBox, the transfer of online and offline donations (Wikando Bank Sync) as well as campaign data is initiated by the FundraisingBox team. Records that were manually created in FundraisingBox are not transferred. #### Scenario 3: Large Data Volumes Existing Only in FundraisingBox For large volumes of data (from approx. 50,000 records/transactions), the FundraisingBox data is first transferred to the CRM system by the implementation partner or the organization's data migration team. In this process, FundraisingBox data must be exported together with the corresponding IDs (fbPerson ID, fbDonation ID, fbRecurringPayment ID, fbFundraisingPage ID) and then imported into the CRM system, for example via manual import. Afterwards, the implementation partner or the organization's data migration team must create an ID mapping documentation, which is handed to the FundraisingBox project team and stored in the connector to correctly match records and prevent duplicates once the inital synchronization has started. #### Scenario 4: FundraisingBox Data Migrated From a Legacy CRM System Into the New CRM System It must be determined where the most up-to-date data resides (legacy CRM system, FundraisingBox, or the new CRM system). If the most current data is not in FundraisingBox, the data in FundraisingBox must first be updated to reflect the current state. Afterwards, FundraisingBox data must be exported (from the leading system) together with the corresponding IDs (fbPerson ID, fbDonation ID, fbRecurringPayment ID, fbFundraisingPage ID) and then imported into the CRM system, for example via manual import. The implementation partner or the organization's data migration team must create an ID mapping documentation, which is handed to the FundraisingBox project team and stored in the connector to correctly match records and prevent duplicates once the inital synchronization has started. ### **Step-by-step Guide for Scenario 3 and 4** * **Starting point:** The most up-to-date data resides in the legading CRM system. * **Data export and import:** FundraisingBox Data is exported from the leading CRM system and imported into the new CRM system. * FundraisingBox data is exported together with the corresponding IDs (fbPerson ID, fbDonation ID, fbRecurringPayment ID, fbFundraisingPage ID). * **ID mapping documentation:** In a CSV file, the FundraisingBox IDs are mapped to the corresponding IDs in the CRM system. The documenation is handed to the FundraisingBox project team (example ID mapping file will be prepared). * **FundraisingBox update:** The data in FundraisingBox is updated to match the state of the new CRM system. * **Connector import:** FundraisingBox project team imports the CSV file with the ID mappings into the connector. **Delta period:** There will be a time gap between the last data transferred via the old process (FundraisingBox → legacy CRM system → new CRM system) and the project Go-Live. Data from this period will be transferred manually at Go-Live by the FundraisingBox project Team. For this purpose, the exact timestamp or the reference to the last donation imported from the legacy CRM system into the new CRM system is required. * **Start of synchronization:** The connector begins synchronizing data between the systems. *** ### Important Steps Before Bidirectional Live Synchronization / Go Live It is strongly recommended to first perform the initial data mapping and synchronization in a test instance of the CRM system. The connector can initially be connected unidirectionally (from the live FundraisingBox to the CRM test instance). This allows all processes to be tested under realistic conditions and potential issues to be identified and resolved at an early stage. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://solutions.fundraisingbox.com/knowledge-base/initial-data-mapping-and-synchronization.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.