Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Transitioning Data from Legacy Systems into QuickBase

Locked deep inside your company, legacy data is the running your business – and holding you back. It’s one of the reasons for the rise of Shadow IT and Citizen Developers. Users today don’t just need access; they need to use that data in ways most enterprise systems can’t provide. We will take a look at how legacy data can be transformed within your organization. Three options will be discussed: Modernized, Integrate, and Migrate. We will show you how tools such as QuickBase Sync and Zapier can unlock your legacy data. We will also show you tools built that allow migration from IBM Notes & Domino and Microsoft SharePoint to QuickBase with just a few clicks! Come learn how to leverage all of your data!

  • Be the first to comment

Transitioning Data from Legacy Systems into QuickBase

  1. 1. Transitioning Data from Legacy Systems to QuickBase John Head & Ken Lamey PSC Group, LLC
  2. 2. ① About Us ② Legacy Data ③ Application Modernization ④ Migration & Integration Options AGENDA
  3. 3. ① What does Application Modernization mean and why do you care? ② What types of applications migrate best to QuickBase? ③ What tools & resources are available to migrate and integrate data to QuickBase? 3 things you will learn in this session
  4. 4. About Us 1
  5. 5. ① Evangelist & Business Development ② 24 years experience – 19 Consulting, 5 sales ③ Speaker at conferences and user groups around the world – 50+ sessions ④ IBM Champion (5 years) ⑤ Specialize in Application Modernization & Integration John Head
  6. 6. ① Consulting Manager for the PSC Group – 17 Years consulting for PSC – QuickBase and Cloud Rapid Application Development Solutions Owner at PSC. ② 24 years of consulting experience architecting, developing and implementing business solutions for over 100 organizations. ③ Experienced in converting, integrating, exporting, importing data between applications on all platforms. Ken Lamey
  7. 7. PSC is a business and IT consulting firm specializingin strategyand integration. We match experienced professionals with proven and emergent technology to design, deliver, and service customized solutions. We turn IT into an effective strategic resource that improves efficiencies and work streams, delivers a measurable return on investment, and grows companies.
  8. 8. TechTarget
  9. 9. Legacy Data 2
  10. 10. In computing, a legacy system is an old method, technology, computer system, or application program, "of, relating to, or being a previous or outdated computer system." Often a pejorative term, referencing a system as "legacy" often implies that the system is out of date or in need of replacement. Source: Definition: Legacy System
  11. 11. ① Many are band-aided together and guarantee business silos. ② Maintenance and staffing costs are high and growing. ③ Compliance and regulatory concerns abound. ④ Limited functionality limits innovation and growth. ⑤ Purely data-driven architecture prohibits access to business content. Pain Points of working with Legacy Systems
  12. 12. ① Unhappy Users ② High Cost ③ Lack of integration; reports & dashboards difficult ④ No chance for innovation Impact of Legacy System Usage
  13. 13. How did we get here? •Doing the same things better Iteration
  14. 14. How did we get here? •Doing the same things better Iteration •Doing new thingsInnovation •Doing new things that make the old ones obsolete Transformation
  15. 15. ① Users are not happy with bad applications ② Users find options to bypass legacy systems ③ Front Office / Systems of Engagement first systems users replace ④ Solves User’s problems; mobile, fast, etc. ⑤ Creates new silos and lack of integration Impact of Shadow IT & Citizen Development
  16. 16. Application Modernization 3
  17. 17. Application Update Pace System of Record vs. System of Engagement Sales and Marketing Customer Service Business Analytics 52% 44% 44% Front Office is moving fast Transaction Processing Data center Consolidation Back Office is lagging Moving to Cloud Not Moving to Cloud 34% 31% 17%19%
  18. 18. The Application Disruptors UX Modern Workflow MobileSocial Cloud
  19. 19. ① Legacy data combines data, presentation, and logic ② Modern development separates these ③ Allows for decoupling, integration, and future modernization ④ Rapid updates from vendors doesn’t impact application (upgrades) Data vs. UX vs. Logic/Workflow
  20. 20. Our Methodology Inventory Existing Application Portfolio Categorize and Prioritize Estimate Modernization Costs Determine Landing Platform Network Impact Analysis Data Center Impact Analysis Define Security Model on Landing Platform Establish Tools & Standards Application Transformation Data Transformation Sunset Legacy Environment Develop Support and Staffing Plan Application Modernized! Reduce Licensing of Legacy Environment Define Governance Model Modify Infrastructure Establish Development Environment Specify and Procure Production Hardware and Software Analysis & Design Prepare for a more data driven, mobile, social and dynamic future Identify opportunities to enhance processes, workflow and security Technical Analysis Business Value Analysis Cultural Change Analysis Develop Training Plan and Materials Train End Users on Modernized Application ANALYZE MODERNIZE
  21. 21. More people have cell phones than running water. 22 Source: have-cell-phones-than-clean-water/ Impact of Mobile
  22. 22. People look at their photos 1,500x each week They spend 177 minutes on their phone per day Source: Image: Image courtesy of adamr / Impact of Social
  23. 23. Decision Point Archive Leave As Is Integrate Migrate / Modernize
  24. 24. Integration: Process of attaining close and seamless coordination between several departments, groups, organizations, systems, etc. Soruce: Migration: involves moving a set of instructions, programs and/or data from one platform to another. Source: Integration vs. Migration
  25. 25. Migration & Integration Options4
  26. 26. Notes/Domino to QuickBase
  27. 27. ① 30+ year old customer base ② Email + Custom Applications ③ Millions of Notes/Domino applications still in use worldwide ④ As companies migrate to other email platforms, application migration opportunity Notes/Domino to QuickBase
  28. 28. ① Document Library (ships with product) ② Discussion Library (ships with product) ③ Teamroom (ships with product) ④ Custom Forms ⑤ Workflow Applications Typical Notes/Domino Apps that Migrate to QuickBase Easily
  29. 29. Demo – Lotus Notes Migration to QuickBase
  30. 30. SharePoint to QuickBase
  31. 31. ① SharePoint is 15 years old ② Started as document library, transition to application platform ③ Microsoft transitioned development model in SP 2013 – Traditional (Server-side) vs. App Model (Client-side) ④ Major shift with Office365 / SharePoint Online SharePoint to QuickBase
  32. 32. Microsoft SharePoint is in a time of transition. IT leaders responsible for SharePoint initiatives must evaluate the specific functional needs they have, as well as their level of risk avoidance. Impacts ① Microsoft's strategic commitment to the cloud with SharePoint Online has created the imperative for IT leaders to re-evaluate SharePoint's role in their workplace technology road map. ② Microsoft's new app model has limited the ability to customize SharePoint Online compared to SharePoint deployed on-premises, so IT leaders must reconsider how to use SharePoint. ③ Microsoft's focus on SharePoint Online means IT leaders have to factor in risk tolerance, organizational culture and migration complexity when assessing its suitability. SharePoint Outlook from the Analysts
  33. 33. Recommendations IT leaders: ① Examine your SharePoint use cases to determine suitable options. SharePoint Online is suitable for a range of use cases, from basic tasks such as file sharing through to highly collaborative, content-centric processes such as RFP development. ② Explicitly revise governance plans and communicate guidance on what SharePoint Online should and should not be used for. ③ Involve your legal, risk and compliance teams to determine whether the risks of SharePoint Online are acceptable to your organization. ④ If SharePoint Online falls short of these measures, consider whether it would make more sense to continue using SharePoint on-premises, choose an alternative vendor/platform or adopt a hybrid approach (on-premises for existing custom workloads, Online for new, more generic work). SharePoint Outlook from the Analysts
  34. 34. ① Document Libraries ② Lists ③ Basic Workflow SharePoint Apps that Migrate to QuickBase Easily
  35. 35. Demo – SharePoint Migration to QuickBase
  36. 36. Integrating with QuickBase
  37. 37. ① Not Application Integration ② Does Not Start with Technology ③ IBM: “Data Integration involves discovery, cleansing, monitoring, transforming and delivery of data from a variety of sources.” Data Integration
  38. 38. • Need a Specific Calculated Approach • Reduce Data Complexity • Improved ROI of Data Through Unified Systems • Increased Access to Data Data Integration Plan • Simplified Data Collaboration • Understanding of Data Means Smarter Business Decisions • Data Integrity Improvements • Make your Data Live
  39. 39. ① QuickBase Sync ② workato ③ Zapier ④ Flow and Others ⑤ Custom QuickBase Integration Tools
  40. 40. Demo – QuickBase Integration
  41. 41. Wrap-up 5
  42. 42. ① What is Application Modernization mean and why we care ② What types of applications migrate best to QuickBase ③ Demonstrations of tools that help you integrate with and migrate to QuickBase What we learned
  43. 43. ThankYou Contact: JohnHead 331.684.7114|