Data migration - Converge Community
<main> <article class="userContent"> <p>In order to migrate data, we have to know the fields you need before we map your legacy data to those fields. We only migrate closed case data, so your company must have a cutoff date, after which no more cases will be put into the old system. After that cutoff date, all new cases must be proxy-ed into Convercent. Then, we can begin the migration of the closed cases. The sooner that you schedule the cutoff date, the sooner we can get all of the closed case data into your system. </p><p>Most customers will experience anywhere between 1-4 weeks of proxy reporting depending on their case volume. We recommend that you have a month overlap between the two systems, giving you time to close everything out and bring over any open cases. Assuming you have both systems, you can begin to use Convercent (by proxy), but also post to your old system with updates on how Reporters can track case information in the new system (Convercent). </p><p>The migration of data consists of several steps:</p><ol><li>Talk to Convercent about your data</li><li>Convercent maps the data</li><li>Convercent uploads data to trial for you to review: This can take time, depending on how quickly you approve this mapping of data. Before getting back to Convercent about what you like and what needs to change, make sure you look at the entire application and send over all of your feedback at once. This decreases the amount of back and forth time.</li><li>Move to production and go live with Convercent!</li></ol><p><strong>Data Migration Type Breakdown</strong></p><p><strong>1. Standard Data Legacy Migration (for reporting purposes)</strong></p><p>This legacy migration is geared towards importing data that is explicitly used in reporting. Data that is not reportable will not be migrated. Due to this being a more predictable data migration method, the timeline and workload is significantly less than that of a custom migration. This migration type will never bring over Issue Message Threads or Attachments, and is primarily focused on digesting data metrics related to open/close dates, issue types, outcomes, actions taken and root cause analysis. </p><p><strong>Timeline:</strong> 3 – 6 weeks depending on loading tool reliability</p><p><strong>2. Custom Legacy Migration</strong></p><p>This legacy migration is to migrate any and all case data, formatted and presented in the application per recommendation of the customer. Custom data transformations are included in this package. Pricing can be influenced by the number of cases and number of attachments.</p><p><strong>Timeline:</strong> 12 – 18 weeks depending on loading tool reliability. Timeline can be significantly impacted based on depth of data transform customization</p><p>For more information on a successful data migration, review this documentation.</p><div class="js-embed embedResponsive" data-embedjson="{"url":"https:\/\/us.v-cdn.net\/6032280\/uploads\/OCAVBT022IUA\/convercent-data-migration-overview.docx","name":"Convercent Data Migration Overview.docx","type":"application\/vnd.openxmlformats-officedocument.wordprocessingml.document","size":28899,"displaySize":"large","float":"none","mediaID":770,"dateInserted":"2021-02-05T19:42:26+00:00","insertUserID":42710,"foreignType":"embed","foreignID":42710,"embedType":"file"}"> <a href="https://us.v-cdn.net/6032280/uploads/OCAVBT022IUA/convercent-data-migration-overview.docx" download="" aria-label="Convercent Data Migration Overview.docx"> Convercent Data Migration Overview.docx </a> </div> <p><br></p> </article> </main>