Patent Publication Number: US-2022217140-A1

Title: Automatic event migration

Description:
CROSS-REFERENCES TO RELATED APPLICATIONS 
     This is a continuation application of and claims priority to U.S. patent application Ser. No. 16/430,412 entitled “AUTOMATIC EVENT MIGRATION” and filed on Jun. 3, 2019 for John Ryan Caldwell, which is a continuation application of and claims priority to U.S. patent application Ser. No. 15/365,941 entitled “AUTOMATIC EVENT MIGRATION” and filed on Nov. 30, 2016 for John Ryan Caldwell, which claims the benefit of U.S. Provisional Patent Application No. 62/261,028 entitled “AUTOMATIC PAYMENT AND DEPOSIT MIGRATION” and filed on Nov. 30, 2015, for John Ryan Caldwell, all of which are incorporated herein by reference in their entirety for all purposes. 
    
    
     FIELD 
     This invention relates to identifying events and more particularly relates to migrating or transferring identified events. 
     BACKGROUND 
     As more and more of a user&#39;s data moves to the cloud, and more and more events or transactions become electronic, it has become increasingly difficult for a user to manage and/or update the user&#39;s own personal electronic events, many of which are automatically repeating and/or recurring. Users may therefore allow the events to continue to occur, even if they&#39;re no longer desired or using a service provider that is no longer optimal. 
     For example, on a hardware device, data may periodically be backed up to a different hardware device over a data network (e.g., a local backup, a cloud backup, or the like), an antivirus or security scan may periodically process the hardware device for threats, subscriptions to cloud services or downloadable software licenses may be automatically renewed and/or automatically paid, software updates may be automatically downloaded and/or installed, and/or other events may periodically occur. A user may easily lose track of repeating and/or recurring events, or may not even have an interface to cancel or change such events. 
     SUMMARY 
     Methods are presented for event migration. In one embodiment, a method includes aggregating a set of events from one or more servers to a trusted hardware device. Certain different events of a set of events may be associated with different service providers. A method, in certain embodiments, includes identifying, on a trusted hardware device, a repeating event from a set of events. A method, in one embodiment, includes prompting a user to migrate subsequent instances of a repeating event from one service provider to a different service provider of a plurality of service providers based on a likelihood that the aggregated set of events includes each event for the user of an event type of the aggregated set of events. In some embodiments, a method includes migrating subsequent instances of a repeating event, using a user&#39;s electronic credentials, from one service provider to a different service provider in response to the user accepting a prompt. 
     Apparatuses are presented for event migration. An apparatus, in one embodiment, includes a trusted hardware device authorized by a user to use a plurality of electronic credentials for the user. A trusted hardware device, in certain embodiments, is configured to aggregate a set of events from one or more servers using one or more electronic credentials for a user. In one embodiment, a trusted hardware device is configured to identify a plurality of repeating events from a set of events. A plurality of repeating events may be associated with a plurality of service providers. A trusted hardware device, in some embodiments, is configured to prompt a user to migrate execution of a plurality of repeating events from a plurality of service providers to a different service provider based on a likelihood that the aggregated set of events includes each event for the user of an event type of the aggregated set of events. In certain embodiments, a trusted hardware device is configured to migrate execution of a plurality of repeating events, using one or more electronic credentials for a user, from a plurality of service providers to a different service provider in response to the user accepting a prompt. 
     Systems are presented for event migration. A backend server, in one embodiment, selects one or more repeating events for at least a subset of a plurality of users based on aggregated sets of events for each of the plurality of users. In certain embodiments, a plurality of event migration modules are located on hardware devices for a plurality of users. In one embodiment, event migration modules are configured to prompt at least a subset of users to migrate one or more selected repeating events to one or more different service providers based on a likelihood that the aggregated set of events includes each event for the user of an event type of the aggregated set of events. A backend server and/or an event migration module, in certain embodiments, is configured to migrate a repeating event to a different service provider in response to a user accepting a prompt associated with the repeating event. 
     An apparatus, in another embodiment, includes means for performing the various steps and operations described with regard to the disclosed methods, apparatuses, and systems. Computer program products comprising a computer readable storage medium are presented. In certain embodiments, a computer readable storage medium stores computer usable program code executable to perform one or more of the operations described with regard to the disclosed methods, apparatuses, and systems. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       In order that the advantages of the invention will be readily understood, a more particular description of the invention briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only typical embodiments of the invention and are not therefore to be considered to be limiting of its scope, the invention will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which: 
         FIG. 1A  is a schematic block diagram illustrating one embodiment of a system for event migration; 
         FIG. 1B  is a schematic block diagram illustrating a further embodiment of a system for event migration; and 
         FIG. 2  is a schematic flow chart diagram of one embodiment of a method for event migration. 
     
    
    
     DETAILED DESCRIPTION 
     Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive and/or mutually inclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise. 
     Furthermore, the described features, advantages, and characteristics of the embodiments may be combined in any suitable manner. One skilled in the relevant art will recognize that the embodiments may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments. 
     These features and advantages of the embodiments will become more fully apparent from the following description and appended claims, or may be learned by the practice of embodiments as set forth hereinafter. As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method, and/or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (e.g., including firmware, resident software, micro-code, etc. stored on a non-transitory computer readable storage medium) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module,” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more non-transitory computer readable storage medium(s) having program code embodied thereon. 
     Many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a logic hardware circuit comprising custom VLSI circuits or gate arrays (e.g., an application specific integrated circuit), off-the-shelf semiconductors such as logic chips, transistors, and/or other discrete components. A module may also be implemented in one or more programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like. 
     Modules may also be implemented at least partially in software for execution by various types of processors. An identified module of program code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module. 
     Indeed, a module of program code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. Where a module or portions of a module are implemented in software, the program code may be stored and/or propagated on in one or more non-transitory computer readable storage media. A computer program product may include a non-transitory computer readable storage medium (or media) storing computer readable program instructions thereon for causing a processor to carry out aspects of the present invention. 
     A computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM”), a semiconductor memory device (e.g., NAND Flash memory, NOR flash memory, nano random access memory (nano RAM or NRAM), nanocrystal wire-based memory, silicon-oxide based sub-10 nanometer process memory, graphene memory, Silicon-Oxide-Nitride-Oxide-Silicon (SONOS), resistive RAM (RRAM), programmable metallization cell (PMC), conductive-bridging RAM (CBRAM), magneto-resistive RAM (MRAM), dynamic RAM (DRAM), phase change RAM (PRAM or PCM), or the like), a static random access memory (“SRAM”), a portable compact disc read-only memory (“CD-ROM”), a digital versatile disk (“DVD”), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and/or any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire. 
     Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers, and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device. 
     Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, script instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, Java, or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user&#39;s computer, partly on the user&#39;s computer, as a stand-alone software package, partly on the user&#39;s computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user&#39;s computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention. 
     These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks. 
     The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks. 
     Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions. 
     The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions of the program code for implementing the specified logical function(s). 
     It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures. 
     Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and program code. 
       FIG. 1A  depicts one embodiment of a system  100  for automated event migration.  FIG. 1B  depicts another embodiment of a system  120  for automated event migration. In one embodiment, the system  120  includes one or more hardware devices  102 , one or more event migration modules  104  (e.g., a backend event migration module  104   b  and/or a plurality of event migration modules  104   a  disposed on the one or more hardware devices  102 ), one or more data networks  106  or other communication channels, one or more service providers  108  (e.g., one or more servers  108  of one or more service providers  108 ; one or more cloud or network service providers  108 ; one or more aggregation servers  108 ; or the like), and/or one or more backend servers  110 . 
     In certain embodiments, even though a specific number of hardware devices  102 , event migration modules  104 , data networks  106 , service providers  108 , and/or backend servers  110  are depicted in  FIG. 1B , one of skill in the art will recognize, in light of this disclosure, that any number of hardware devices  102 , event migration modules  104 , data networks  106 , service providers  108 , and/or backend servers  110  may be included in the system  100  for event migration. For example,  FIG. 1A  depicts a single trusted hardware device  102  and/or  110  comprising a single event migration module  104  in communication with one or more servers  108  over a data network  106 . 
     In one embodiment, the system  100  and/or  120  includes one or more hardware devices  102 . The hardware devices  102  (e.g., computing devices, information handling devices, or the like) may include one or more of a desktop computer, a laptop computer, a mobile device, a tablet computer, a smart phone, a set-top box, a gaming console, a smart TV, a smart watch, a fitness band, an optical head-mounted display (e.g., a virtual reality headset, smart glasses, or the like), an HDMI or other electronic display dongle, a personal digital assistant, and/or another computing device comprising a processor (e.g., a central processing unit (CPU), a processor core, a field programmable gate array (FPGA) or other programmable logic, an application specific integrated circuit (ASIC), a controller, a microcontroller, and/or another semiconductor integrated circuit device), a volatile memory, and/or a non-volatile storage medium. In certain embodiments, the hardware devices  102  are in communication with one or more servers  108  of one or more service providers  108  (e.g., third party servers  108  and/or third party service providers  108 ) and/or one or more backend servers  110  (e.g., first party servers  110  of a first party service provider  108 , of an event migration module  104   b , or the like) via a data network  106 , described below. The one or more hardware devices  102 , in a further embodiment, are capable of executing various programs, program code, applications, instructions, functions, or the like. 
     In one embodiment, an event migration module  104  is configured to switch, migrate, and/or transfer execution of one or more events between service providers  108 . An event migration module  104  may identify an event to migrate by processing aggregated data (e.g., an aggregated set of events) from one or more servers  108  (e.g., downloaded from one or more third party service providers  108 , from one or more first party service providers  108  associated with the backend server  110 , from one or more aggregation servers  108 , and/or the like). An event migration module  104  may identify one or more repeating events from a set of events, prompt a user to migrate one or more repeating events from one service provider  108  to a different service provider  108 , and/or migrate one or more repeating events to a different service provider  108 , or the like. 
     Many users may desire to switch service providers  108 . However, service providers  108  may make the process difficult, or users may not want to go through the headache of making the switch, even if a different service provider  108  provides better features, quality, price, or another attribute than a current service provider  108 . An event migration module  104 , in certain embodiments, identifies repeating events associated with a service provider  108 , and provides an interface allowing a user to switch or migrate the event to a different service provider  108  (e.g., a different software as a service (SaaS) provider; a different data repository; a different social network; a different payment source such as a debit card, credit card, financial account, online payment system account, or the like; a different entity and/or institution; or the like). 
     An event migration module  104  may comprise and/or be part of a trusted hardware device  102 ,  110 , which is secure and authorized by a user to store and/or use one or more of the user&#39;s electronic credentials or other important data. An event migration module  104  may be provided by a government entity, an educational institution, a financial institution, and/or another entity which the user trusts and/or authorizes to act in its behalf. For example, an event migration module  104  may be provided by a service provider  108  associated with the backend server  110 , allowing users to migrate and/or switch one or more events from other third party service providers  108  to the first party service provider  108  providing the event migration module  104  (e.g., a social network  108 &#39;s application or website may provide an event migration module  104  as a browser plugin, a mobile application, installable software, or the like that prompts a user to migrate and/or switch a social media post to the social network, in response to identifying repeated posts to a different social network; a financial institution  108 &#39;s mobile application and/or website may prompt a user to switch one or more repeating payments from a credit card, debit card, checking account, savings account, or other financial account of a competitor  108  to a credit card, debit card, checking account, savings account, or other financial account of the financial institution  108 ; an operating system for a hardware device  102  may comprise an event migration module  104  that identifies repeating antivirus scans, data backups, or other events, and may prompt a user to migrate and/or switch the identified events from a third party service provider  108  to a service provider  108  associated with the operating system; or the like). 
     In this manner, one or more event migration modules  104  may automate and/or simplify the migration of events from one service provider  108  to a different service provider  108 , with minimal interaction with a user (e.g., accepting a prompt, providing and/or authorizing use of electronic credentials, or the like), rather than requiring a user to contact a service provider  108  to manually migrate or transfer execution of an event. 
     An event, as used herein, may comprise a detected and/or recorded electronic occurrence or the like associated with a user, a user&#39;s hardware device  102 , a user&#39;s account, or the like. An event, in various embodiments, may occur on and/or may be detected and/or recorded by an event migration module  104 , a service provider  108 , a backend server  110 , a hardware device  102  of a user, one or more sensors, or the like. For example, in various embodiments, an event may comprise one or more of a data backup event for a hardware device  102  of a user over a data network  106  (e.g., to a service provider  108 ), an antivirus and/or security scan event for a hardware device  102  of a user (e.g., periodically scanning files and/or data storage of a hardware device  102  to locate one or more viruses, malware, bots, worms, rootkits, and/or other security risks using software and/or definitions provided by one or more service providers  108 ), a software and/or firmware update event for a hardware device  102  of a user (e.g., an operating system update, a software patch, an application update, and/or another update downloaded and/or installed from a service provider  108  over a data network  106 ), an electronic subscription event for a data network service (e.g., a renewal, a payment, or the like), an electronic transaction event (e.g., a credit or debit card payment, a direct deposit, an electronic bill payment, an automated clearing house (ACH) payment, an online and/or electronic money transfer, a mobile and/or wireless payment, or the like to a website, merchant, vendor, individual, and/or other entity), or the like. 
     A subscription event may include renewing a subscription, paying for a subscription, or the like. A data network service may comprise a digital and/or electronic service that may occur over and/or using a data network  106 , such as a cloud software and/or software as a service (SaaS) subscription, a streaming and/or downloadable media subscription (e.g., video, audio, e-books, or the like), an internet service subscription, a cable television subscription, a subscription made over a data network  106  for delivery of digital and/or physical goods and/or services, or the like. 
     A repeating event may comprise an event that occurs more than once. Different occurrences of a repeating event, in certain embodiments, may comprise at least one attribute in common (e.g., and/or may have one or more attributes that are different). For example, different occurrences of a repeating event may be associated with the same service provider  108 , website, and/or other entity; may occur on or around the same time, periodically (e.g., at or around the same time each day; on the same day and/or within a few days each week, month, quarter, year, or other time period; or the like); may be associated with the same or similar (e.g., within a predefined percentage or amount) transaction amount; and/or have one or more other similarities. An event migration module  104  may be configured to select one or more repeating events having at least a threshold number of similarities, may only select one or more repeating events having one or more required similarities, or the like. In one embodiment, an event migration module  104  may provide an interface (e.g., a graphical user interface (GUI), an application programming interface (API), a command line interface (CLI), and/or another interface) allowing a user (e.g., an end user on a hardware device  102 , an administrator of a backend server  110 , or the like) to select or otherwise define one or more rules for the event migration module  104  to identify one or more repeating events, such as a rule defining a threshold number of similarities for a repeated event, a rule requiring one or more similarities for a repeated event, a rule allowing one or more differences for a repeated event, or the like. 
     In certain embodiments, a recurring event is a type of repeated event with one or more predefined similarities, such as a repeated event that occurs on or around the same time during each of a plurality of time periods (e.g., at or around the same time each day; on the same day and/or within a few days each week, month, quarter, year, or other time period; or the like) and/or is associated with the same or similar (e.g., within a predefined percentage or amount) transaction amount, or the like. In one embodiment, an event migration module  104  may be configured to identify any repeating event (e.g., including recurring and non-recurring events/transactions). In a further embodiment, an event migration module  104  may be configured to identify only recurring events/transactions. 
     An event migration module  104 , in one embodiment, may download, aggregate, and/or otherwise collect or receive a set of events (e.g., a log, a listing, a history, a file, a data structure, and/or another record of one or more events), in which the event migration module  104  may identify one or more repeating events or the like for migrating and/or switching. For example, an event migration module  104  may aggregate events comprising a user&#39;s posts to one or more social media networks  108 , may aggregate system and/or application logs from one or more hardware devices  102 , may aggregate events from one or more electronic calendar or scheduling services  108 , may aggregate images from one or more image sharing and/or backup services  108 , may aggregate financial transactions from one or more financial institutions  108 , may aggregate online orders from one or more e-commerce services  108 , and/or may aggregate a set of events from one or more servers  102 ,  108 ,  110 . 
     An event migration module  104 , in one embodiment, may download and/or aggregate a set of events directly from one or more servers  108  of one or more service providers  108  (e.g., using a user&#39;s electronic credentials for a specific service provider  108  to access an API, CLI, web interface by web crawling and/or screen scraping, or the like). In a further embodiment, an event migration module  104  may download and/or aggregate a set of event from one or more intermediaries, such as an aggregation server  108  that provides access to event data from one or more other service providers  108  (e.g., an event migration module  104  may provide a user&#39;s electronic credentials to an aggregation server  108  or other intermediary which may have access to multiple other service providers  108  and may provide event data from one or more of the other service providers  108  to the event migration module  104 ). In light of this specification, one of skill in the art will recognize many sources which an event migration module  104  may use to aggregate a set of events from one or more servers  108  to a trusted device  102 ,  110 . 
     For example, in one embodiment, an event migration module  104   b  is disposed on a backend server  110 , and may aggregate sets of events for a plurality of different users (e.g., using and/or associated with different hardware devices  102  and/or event migration modules  104   a ) at a central location comprising the backend server  110 . In a further embodiment, a distributed and/or decentralized array of multiple event migration modules  104   a  may each download and/or aggregate a set of events for individual users on the users&#39; own hardware devices  102 . 
     An event migration module  104 , in certain embodiments, may determine and/or receive a user&#39;s electronic credentials (e.g., username and password, fingerprint scan, retinal scan, digital certificate, personal identification number (PIN), challenge response, security token, hardware token, software token, DNA sequence, signature, facial recognition, voice pattern recognition, bio-electric signals, two-factor authentication credentials, or the like) for one or more service providers  108 . An event migration module  104 , in certain embodiments, accesses a server  108  of a service provider  108  using a user&#39;s electronic credentials to download event data associated with the user from the server  108 , such as a user&#39;s photos, a user&#39;s social media posts, a user&#39;s medical records, a user&#39;s financial transaction records or other financial data, and/or other data associated with and/or owned by a user but stored by a server  108  of a third party service provider  108  (e.g., stored by hardware not owned, maintained, and/or controlled by the user). An event migration module  104 , in various embodiments, may provide the downloaded data to the user locally (e.g., displaying the data on an electronic display of a hardware device  102 ); may provide the downloaded data from the hardware device  102  of the user to and/or package the data for a remote server  110  (e.g., a backend event migration module  104   b ) or other remote device (e.g., another hardware device  102  of the user, a hardware device  102  of a different user, or the like) which may be unaffiliated with the third party service provider  108 ; may provide one or more prompts, alerts, messages, advertisements, or other communications to the user (e.g., on a hardware device  102 ) based on the downloaded data; or the like. 
     In certain embodiments, the system  100  and/or  120  includes a plurality of event migration modules  104  disposed/located on hardware devices  102  of a plurality of different users (e.g., comprising hardware of and/or executable code running on one or more hardware devices  102 ). The plurality of event migration modules  104  may act as a distributed and/or decentralized system  100 , executing across multiple hardware devices  102 , which are geographically dispersed and using different IP addresses, each downloading and/or aggregating event data (e.g., photos, social media posts, medical records, financial transaction records, other financial data, and/or other user data) separately, in a distributed and/or decentralized manner. While a third party service provider  108  (e.g., a financial institution, bank, credit union, and/or other online banking provider; a social media site; a medical provider; a photo hosting site; or the like) may block a data aggregation service or other entity from accessing data for a plurality of users from a single location (e.g., a single IP address, a single block of IP addresses, or the like), a distributed and/or decentralized swarm of many event migration modules  104 , in certain embodiments, may be much more difficult for a third party service provider  108  to block. 
     In one embodiment, a hardware device  102  may include and/or execute an internet browser, which a user may use to access a server  108  of a service provider  108  (e.g., by loading a webpage of the third party service provider  108  in the internet browser). At least a portion of an event migration module  104 , in certain embodiments, may comprise a plugin to and/or an extension of an internet browser of a user&#39;s personal hardware device  102 ; so that the event migration module  104  may monitor and/or aggregate events associated with the browser; so that a third party service provider  108  may not block the event migration module  104  from accessing the server  108  of the third party service provider  108  without also blocking the user&#39;s own access to the server  108  using the internet browser; or the like. For example, an event migration module  104  may use the same cookies, IP address, saved credentials, or the like as a user would when accessing a server  108  of a third party service provider  108  through the internet browser. In certain embodiments, an event migration module  104  may support integration with multiple different types of internet browsers (e.g., on different hardware devices  102 ). 
     An event migration module  104 , in certain embodiments, may mimic or copy a user&#39;s behavioral pattern in accessing a server  108  of a third party service provider  108 , to reduce a likelihood that the third party service provider  108  may distinguish access to the server  108  by an event migration module  104  from access to the server  108  by a user. For example, an event migration module  104  may visit one or more locations (e.g., webpages) of a server  108  of a third party service provider  108 , even if the event migration module  104  does not intend to download data from each of the one or more locations, may wait for a certain delay time between accessing different locations, may use a certain scroll pattern, or the like, to mask the event migration module  104 &#39;s downloading and/or aggregating of a user&#39;s data, to reduce the chances of being detected and/or blocked by the third party service provider  108 . 
     In one embodiment, at least a portion of an event migration module  104  may be integrated with or otherwise part of another application executing on a hardware device  102 , such as a personal financial management application (e.g., computer executable code for displaying a user&#39;s financial transactions from multiple financial institutions, determining and/or displaying a user&#39;s financial budgets and/or financial goals, determining and/or displaying a user&#39;s account balances, determining and/or displaying a user&#39;s net worth, or the like), a photo viewer, a medical application, an insurance application, an accounting application, a social media application, or the like, which may use event data the event migration module  104  downloads from a server  108  of a third party service provider  108 , which may generate event data for the event migration module  104 , or the like. 
     In one embodiment, the event migration modules  104   a  comprise a distributed system  100 , with the event migration modules  104   a  and/or the associated hardware devices  102  downloading and/or aggregating event data substantially independently (e.g., downloading data concurrently or non-concurrently, without a global clock, with independent success and/or failure of components). Distributed event migration modules  104   a  may pass messages to each other and/or to a backend event migration module  104   b , to coordinate their distributed aggregation of event data for users, to migrate identified events to different service providers  108 . In one embodiment, the event migration modules  104   a  are decentralized (e.g., hardware devices  102  associated with users perform one or more aggregation functions such as downloading event data), rather than relying exclusively on a centralized server or other device to perform one or more aggregation functions. In another embodiment, a centralized backend server  110  (e.g., a backend event migration module  104   b ) downloads event data and/or performs one or more aggregation functions for a plurality of users and/or user hardware devices  102  (e.g., comprising and/or executing frontend event migration modules  104   a ) using a centralized, non-distributed approach (e.g., with a plurality of frontend event migration modules  104   a  providing an interface on the hardware devices  102  of the users to access functions provided by the backend event migration module  104   b , or the like). 
     In a distributed and/or decentralized system  100 , a central entity, such as a backend event migration module  104   b  and/or a backend server  110 , in certain embodiments, may still provide, to one or more event migration modules  104   a , one or more messages comprising instructions for accessing a server  108  of a service provider  108  using a user&#39;s electronic credentials, instructions for migrating and/or switching one or more repeating events to a different service provider  108 , or the like. For example, a backend event migration module  104   b  may provide one or more event migration modules  104   a  of one or more hardware devices  102  with one or more sets of instructions for accessing a server  108  of a service provider  108 , such as a location for entering a user&#39;s electronic credentials (e.g., a text box, a field, a label, a coordinate, or the like), an instruction for submitting a user&#39;s electronic credentials (e.g., a button to press, a link to click, or the like), one or more locations of event data associated with a user (e.g., a row in a table or chart, a column in a table or chart, a uniform resource locator (URL) or other address, a coordinate, a label, or the like), a location for entering information associated with a different service provider  108  (e.g., a text box, a field, a label, a coordinate, or the like for entering a different debit or credit card number issued by and/or an account number provided by the different service provider  108 , for entering a URL or other address of the different service provider  108 , for entering instructions to use the different service provider  108 , or the like depending on a type of repeating event and/or a type of the different service provider  108 ), an instruction for submitting information associated with the different service provider  108  (e.g., a button to press, a link to click, or the like), and/or other instructions or information, using which the event migration modules  104   a  may access and download a user&#39;s event data, migrate a repeating event, or the like. 
     In a further embodiment, one or more event migration modules  104   a  may pass messages to each other, such as instructions for accessing a server  108  of a service provider  108  (e.g., to aggregate event data, to migrate a repeating event, or the like) using a user&#39;s credentials, or the like, in a peer-to-peer manner. In another embodiment, a central entity, such as a backend event migration module  104   b , may initially seed one or more sets of instructions for accessing a server  108  of a third party service provider  108  using a user&#39;s credentials to one or more event migration modules  104   a , and the one or more event migration modules  104   a  may send the one or more sets of instructions to other event migration modules  104   a.    
     Instructions for accessing a user&#39;s event data and/or for migrating a repeating event to a different service provider  108 , however, in certain embodiments, may change over time, may vary for different users of a service provider  108 , or the like (e.g., due to upgrades, different service levels or servers  108  for different users, acquisitions and/or consolidation of different third party service providers  108 , or the like), causing certain instructions to fail over time and/or for certain users, preventing an event migration module  104  from aggregating a user&#39;s event data and/or migrating a repeating event. A backend event migration module  104   b , in one embodiment, may provide one or more event migration modules  104   a  with a hierarchical list of multiple sets of instructions, known to have enabled access to a user&#39;s event data from a server  108  of a service provider  108  and/or migration of a repeating event to a different service provider  108 . An event migration module  104   a  on a hardware device  102  may try different sets of instructions in hierarchical order, until the event migration module  104   a  is able to access a user&#39;s event data, migrate a repeating event, or the like. 
     An event migration module  104 , in certain embodiments, may provide an interface to a user allowing the user to repair or fix failed instructions for accessing the user&#39;s event data and/or migrate a repeating event, by graphically identify an input location for the user&#39;s electronic credentials, an instruction for submitting a user&#39;s electronic credentials, a location of event data associated with the user, an input location for information of a different service provider  108 , an instruction for submitting the information of the different service provider  108 , or the like. An event migration module  104 , in one embodiment, may highlight or otherwise suggest (e.g., bold, color, depict a visual comment or label, or the like) an estimate which the event migration module  104  has determined of an input location for the user&#39;s electronic credentials, an instruction for submitting a user&#39;s electronic credentials, a location of event data associated with the user, an input location for information of a different service provider  108 , an instruction for submitting the information of the different service provider  108 , or the like. For example, an event migration module  104  may process a web page of a server  108  of a service provider  108  (e.g., parse and/or search a hypertext markup language (HTML) file) to estimate an input location for the user&#39;s electronic credentials, an instruction for submitting a user&#39;s electronic credentials, a location of event data associated with the user, an input location for information of a different service provider  108 , an instruction for submitting the information of the different service provider  108  or the like. 
     The one or more event migration modules  104 , in certain embodiments, may provide an interface (e.g., an API, GUI, CLI, or the like) to provide downloaded and/or aggregated event data from servers  108  of one or more third party service providers  108  to one or more other entities (e.g., a remote server  110  or other hardware device  102  unaffiliated with the third party service provider  108 , a backend event migration module  104   b , or the like). The interface, in one embodiment, comprises a private interface between event migration modules  104   a  of users&#39; hardware devices  102  and one or more backend event migration modules  104   b . For example, this may enable a backend event migration module  104   b  to provide a user with access to downloaded and/or aggregated event data and/or to prompt a user to migrate a repeated event at multiple locations, on multiple hardware devices  102 , through multiple channels, or the like, even if the user&#39;s hardware device  102  which downloaded the data is turned off, out of battery, not connected to the data network  106 , or the like. In another embodiment, the interface comprises a public and/or open interface, which may be secured, allowing a user to share the user&#39;s downloaded event data from an event migration module  104  to one or more other tools, services, and/or other entities to store, process, and/or otherwise use the data. 
     In various embodiments, an event migration module  104  may be embodied as hardware, software, or some combination of hardware and software. In one embodiment, an event migration module  104  may comprise executable program code stored on a non-transitory computer readable storage medium for execution on a processor of a hardware device  102 , a backend server  110 , or the like. For example, an event migration module  104  may be embodied as executable program code executing on one or more of a hardware device  102 , a backend server  110 , a combination of one or more of the foregoing, or the like. In such an embodiment, the various modules that perform the operations of an event migration module  104 , as described below, may be located on a hardware device  102 , a backend server  110 , a combination of the two, and/or the like. 
     In various embodiments, an event migration module  104  may be embodied as a hardware appliance that can be installed or deployed on a backend server  110 , on a user&#39;s hardware device  102  (e.g., a dongle, a protective case for a phone  102  or tablet  102  that includes one or more semiconductor integrated circuit devices within the case in communication with the phone  102  or tablet  102  wirelessly and/or over a data port such as USB or a proprietary communications port, or another peripheral device), or elsewhere on the data network  106  and/or collocated with a user&#39;s hardware device  102 . In certain embodiments, an event migration module  104  may comprise a hardware device such as a secure hardware dongle or other hardware appliance device (e.g., a set-top box, a network appliance, or the like) that attaches to another hardware device  102 , such as a laptop computer, a server, a tablet computer, a smart phone, or the like, either by a wired connection (e.g., a USB connection) or a wireless connection (e.g., Bluetooth®, Wi-Fi®, near-field communication (NFC), or the like); that attaches to an electronic display device (e.g., a television or monitor using an HDMI port, a DisplayPort port, a Mini DisplayPort port, VGA port, DVI port, or the like); that operates substantially independently on a data network  106 ; or the like. A hardware appliance of an event migration module  104  may comprise a power interface, a wired and/or wireless network interface, a graphical interface (e.g., a graphics card and/or GPU with one or more display ports) that outputs to a display device, and/or a semiconductor integrated circuit device as described below, configured to perform the functions described herein with regard to an event migration module  104 . 
     An event migration module  104 , in such an embodiment, may comprise a semiconductor integrated circuit device (e.g., one or more chips, die, or other discrete logic hardware), or the like, such as a field-programmable gate array (FPGA) or other programmable logic, firmware for an FPGA or other programmable logic, microcode for execution on a microcontroller, an application-specific integrated circuit (ASIC), a processor, a processor core, or the like. In one embodiment, an event migration module  104  may be mounted on a printed circuit board with one or more electrical lines or connections (e.g., to volatile memory, a non-volatile storage medium, a network interface, a peripheral device, a graphical/display interface. The hardware appliance may include one or more pins, pads, or other electrical connections configured to send and receive data (e.g., in communication with one or more electrical lines of a printed circuit board or the like), and one or more hardware circuits and/or other electrical circuits configured to perform various functions of an event migration module  104 . 
     The semiconductor integrated circuit device or other hardware appliance of an event migration module  104 , in certain embodiments, comprises and/or is communicatively coupled to one or more volatile memory media, which may include but is not limited to: random access memory (RAM), dynamic RAM (DRAM), cache, or the like. In one embodiment, the semiconductor integrated circuit device or other hardware appliance of an event migration module  104  comprises and/or is communicatively coupled to one or more non-volatile memory media, which may include but is not limited to: NAND flash memory, NOR flash memory, nano random access memory (nano RAM or NRAM), nanocrystal wire-based memory, silicon-oxide based sub-10 nanometer process memory, graphene memory, Silicon-Oxide-Nitride-Oxide-Silicon (SONOS), resistive RAM (RRAM), programmable metallization cell (PMC), conductive-bridging RAM (CBRAM), magneto-resistive RAM (MRAM), dynamic RAM (DRAM), phase change RAM (PRAM or PCM), magnetic storage media (e.g., hard disk, tape), optical storage media, or the like. 
     The data network  106 , in one embodiment, includes a digital communication network that transmits digital communications. The data network  106  may include a wireless network, such as a wireless cellular network, a local wireless network, such as a Wi-Fi network, a Bluetooth® network, a near-field communication (NFC) network, an ad hoc network, and/or the like. The data network  106  may include a wide area network (WAN), a storage area network (SAN), a local area network (LAN), an optical fiber network, the internet, or other digital communication network. The data network  106  may include two or more networks. The data network  106  may include one or more servers, routers, switches, and/or other networking equipment. The data network  106  may also include one or more computer readable storage media, such as a hard disk drive, an optical drive, non-volatile memory, RAM, or the like. 
     The one or more service providers  108 , in one embodiment, may include one or more network accessible computing systems such as one or more web servers hosting one or more web sites, an enterprise intranet system, an application server, an application programming interface (API) server, an authentication server, or the like. The one or more service providers  108  may include systems related to various institutions or organizations. For example, a service provider  108  may include a system providing electronic access to a financial institution, a university, a government agency, a utility company, an email provider, a social media site, a photo sharing site, a video sharing site, a data storage site, a medical provider, a SaaS provider, a software publisher, a subscription media provider (e.g., a streaming and/or downloadable audio, video, and/or e-book provider), an e-commerce website, and/or another entity providing a service associated with one or more repeating events. A service provider  108  may allow users to create user accounts associated with one or more repeating events (e.g., uploads, purchases, transactions, subscription events, data backup events, antivirus scans and/or updates, or the like). Accordingly, a service provider  108  may include an authorization system, such as a login element or page of a web site, application, API, or similar front-end, where a user can provide credentials, such as a username/password combination, to access the user&#39;s event data, to access services of the service provider  108 , or the like. 
     An event migration module  104 , in certain embodiments, may aggregate a set of events from one type of service provider  108  in order to identify and migrate repeating events for another type of service provider  108 . For example, an event migration module  104  may aggregate financial transactions from one or more financial institution service providers  108  that have issued debit and/or credit cards to a user; where a user has a checking, savings, or other financial account; or the like in order to identify repeating events for one or more other types of service providers  108  (e.g., a SaaS provider, a software publisher, a subscription media provider, an e-commerce website, a merchant, a vendor, a mobile wallet provider, an antivirus provider, a utility company, an email provider, a social media site, a photo sharing site, a video sharing site, a data storage site, a medical provider, or the like). An event migration module  104  may use a first set of electronic credentials of a user to aggregate a set of events (e.g., directly and/or indirectly from one or more financial institutions to aggregate financial transaction data comprising financial transaction events) and, in response to identifying a repeated event, prompting a user to migrate the repeated event, and receiving authorization from the user accepting the prompt, the event migration module  104  may use a second set of electronic credentials of the user to migrate the repeated event to a different service provider  108  (e.g., using a user&#39;s electronic credentials for a streaming video service such as Netflix® to change the default payment source to a credit or debit card associated with a different financial institution service provider  108 , or the like). 
     An event migration module  104  may be configured to process aggregated and/or downloaded event data to identify one or more repeating events. For example, an event migration module  104  may identify common and/or similar text strings in records for different instances of a repeating event (e.g., a text string associated with the same service provider  108 ), may identify a pattern in timing (e.g., time of day, day of the week, day of the month, day of the year, week of the year, month of the year, or the like) based on a timestamp or other date record for a repeating event, may correlate numerical values for different instances of a repeating event (e.g., the same value or within a threshold amount of the same value; the same monetary amount or within a threshold amount of the same monetary amount; or the like), may identify a similar event identifier and/or service provider  108  identifier (e.g., a name, URL or other address, or the like), may use artificial intelligence and/or machine learning to correlate event data into one or more repeating events, and/or may otherwise identify one or more repeating events. 
     A central event migration module  104   b , in certain embodiments, may process aggregated sets of events for multiple users (e.g., each of a service provider  108 &#39;s users, or the like) to identify repeating events and may dynamically target and/or select certain repeated events for certain users based on the aggregated sets of events. For example, in one embodiment, an event migration module  104  may determine whether or not to prompt a user to migrate a repeating event (e.g., subsequent instances of a repeating event identified in historical aggregated sets of event data) based on a likelihood that an aggregated set of events for the user includes each event for the user of an event type of the aggregated set of events (e.g., all or substantially all of a user&#39;s social media posts from all of the user&#39;s social media accounts, all or substantially all of a user&#39;s financial transactions from all of the user&#39;s financial accounts, or the like). In a further embodiment, instead of and/or in addition to being based on a likelihood that an aggregated set of events for the user includes each event for the user of an event type, an event migration module  104  may determine whether or not to prompt a user to migrate a repeating event to a different service provider  108  based on an estimated value to the different service provider  108  of migrating the repeating event (e.g., of migrating subsequent instances of the repeating event) based on values associated with the repeated event in the aggregated set of events for the user. 
     In one embodiment, an event migration module  104  selects a user for migrating a repeating event and/or selects a repeating event for migrating in response to the user&#39;s event data satisfying an event metric associated with the repeating event (e.g., associated by event type, by service provider  108 , or the like). As used herein, an event metric may include a measurable or estimable quantity or unit of a repeating event that can be used to select a user and/or a repeating event for migrating to a different service provider  108 . An event metric, in various embodiments, may include a lifetime value metric, a total spend metric, a transaction interval metric, an interest rate for a repeating event, a sum total spent on a repeating event, a price per repeating event, a monthly payment amount for a repeating event, a profit margin for a repeating event, a fee for a repeating event a geographical event metric, an income metric for a user associated with a repeating event, a savings metric associated with a repeating event, and/or the like. 
     An event metric, in one embodiment, comprises a lifetime value metric indicating a projected and/or estimated total value of a user to a different service provider  108  to which a repeating event is migrated (e.g., based on the user&#39;s aggregated set of events and/or on a cost of the migration to the different service provider  108 ), or the like. For example, an event migration module  104  may determine and/or estimate, based on a user&#39;s aggregated set of events, an amount the user is likely to spend on subsequent instances of the repeating event (e.g., based on previous costs and/or profits associated with the repeating event), how loyal a user is likely to be to the different service provider  108  after the migration (e.g., based on a determined amount of time the user has used the previous service provider  108 , how often the user has previously migrated the repeating event, or the like), or the like, and may determine a lifetime value metric based on one or more of the foregoing determinations. 
     An event metric, in certain embodiments, comprises a total spend metric indicating a confidence of whether a user&#39;s aggregated set of events includes each of the user&#39;s events of an associated event type (e.g., each of the user&#39;s financial transactions from multiple financial institutions  108  for aggregated financial data, each of the user&#39;s social media posts from multiple social media networks  108  for aggregated social media data, or the like), aggregated from multiple entities (e.g., banks, credit unions, credit card companies or other lenders, payment processing companies, online payment providers, and/or the like for financial transaction events). If there is a low confidence or probability that an event migration module  104  has access to each of the user&#39;s events of a certain type (e.g., a complete and/or substantially complete financial snapshot for the user for aggregated financial transactions), it may be unlikely that an event migration module  104 &#39;s determination of whether the user&#39;s financial transaction data satisfies an event metric associated with a repeating event is accurate, and a new service provider  108  may therefore find the user a poor candidate for migrating the repeating event, due to the uncertainty of whether the user&#39;s aggregated event data is complete. Conversely, if there is a high confidence or probability that an event migration module  104  has access to each of a user&#39;s events for the user of an event type (e.g., a complete and/or substantially complete financial snapshot for the user for aggregated financial transactions), a new service provider  108  may have greater trust in an event migration module  104 &#39;s selection of the user, and may prompt the user to migrate the repeating event with greater certainty. 
     An event migration module  104 , in certain embodiments, may analyze and/or process a user&#39;s aggregated set of events using one or more rules, flags, indicators, and/or the like, to determine a total spend metric indicating a confidence of whether the user&#39;s aggregated set of events includes each of the user&#39;s events of an event type (e.g., over a predefined period). For example, in one embodiment, an event migration module  104  may start at a default confidence level (e.g., 50%, 0.5, 0%, 0, 100%, 1, or the like) and may adjust the confidence level for a user&#39;s aggregated set of events based on one or more confidence factors. An event migration module  104 , in certain embodiments, may decrease a confidence level if one event in an event pair (e.g., two events that are often seen together within a predefined period) is missing, may increase a confidence level if both events in an event pair are present, or the like. For example, an event pair may include a mortgage payment and a utility payment; a payment credit on a credit card statement and a corresponding debit from a bank account; a car payment and fuel purchases; and/or another event pair. 
     In a further embodiment, an event migration module  104  may increase a confidence level of a total spend metric if one or more predefined key events are present, and/or may decrease a confidence level of a total spend metric if one or more predefined key events are not present in the aggregated set of events for a user. A key event, in one embodiment, comprises an event that is expected to occur for each user within a predefined period. For example, a key event may comprise a direct deposit and/or payroll check deposit, a mortgage and/or rent payment, at least a threshold amount spent on a personal necessity (e.g., food), and/or another expected event or transaction. In certain embodiments, an event migration module  104  may be configured to prompt a user to add one or more additional accounts for one or more additional service providers  108  in response to determining a confidence level below a threshold for a total spend metric for the user. In another embodiment, an event migration module  104  may query a user whether the user&#39;s aggregated set of events includes each of the user&#39;s events for an event type, and may base a confidence level of a total spend metric on the user&#39;s answer. 
     An event migration module  104 , in one embodiment, may determine a confidence level of a total spend metric and/or another event metric by processing users&#39; aggregated set of events using one or more predefined rules, or the like. In a further embodiment, an event migration module  104  may determine a confidence level of a total spend metric and/or another event metric dynamically, using machine learning or other artificial intelligence, or the like, causing an accuracy of an event migration module  104 &#39;s determinations to increase over time (e.g., at least up to a point) as an event migration module  104  learns from and detects patterns in the aggregated set of events. 
     A geographical event metric, in various embodiments, may indicate, based on a user&#39;s aggregated event data, a geographical location of a user, of a repeating event, of a current service provider  108  for a repeating event, or the like. A geographic region, in certain embodiments, may comprise a street, a development, a district, a city, a county, a state, and/or another identifiable geographic area. 
     An event metric, in one embodiment, may comprise an income metric indicating a user&#39;s income (e.g., monthly, yearly, by source, gross income, disposable income, and/or the like). In a further embodiment, an event metric may comprise a savings metric indicating an amount of money a user saves (e.g., balance of a savings account; balance of an investment account; aggregated total of several savings and/or investment accounts; total amount saved; amount saved over a time period such as daily, weekly, monthly, and/or yearly; a rate of saving; and/or the like). 
     An event metric, in one embodiment, comprises a consistency metric indicating an amount of variation in spending for different events in a series of repeating events. An event metric, in certain embodiments, may comprise a transaction interval metric indicating an amount of time spanned by a user&#39;s aggregated set of events (e.g., one month, two months, three months, six months, a year, two years, three years, and/or the like). For example, in one embodiment, a new service provider  108  for a long term or high valued repeating event, may prefer to prompt one or more users with a higher transaction interval metric (e.g., with a longer amount of time spanned by the users&#39; aggregated set of events), while a new service provider  108  for a smaller value repeating event, may not have such a preference and my prompt users with a lower transaction interval metric (e.g., with a shorter amount of time spanned by the users&#39; aggregated set of events). 
     In certain embodiments, an event migration module  104  may provide an interface (e.g., a graphical user interface (GUI), an application programming interface (API), a command line interface (CLI), and/or the like) for an administrator or other user associated with a service provider  108  to set one or more thresholds whereby a user&#39;s aggregated set of events may satisfy an event metric for migrating a repeating event to the service provider  108 . By setting one or more thresholds whereby a user&#39;s aggregated set of events may satisfy an event metric, a service provider  108  may target certain users for migrating repeating events based on the users&#39; history of events. An event migration module  104 , in one embodiment, may allow a service provider  108  to select a cap and/or a minimum on a number of users that will receive a prompt to migrate a repeating event, to adjust one or more thresholds of an event metric until at least a minimum number of users are selected, and/or the like. 
     In one embodiment, the one or more backend servers  110  and/or one or more backend event migration modules  104   b  provide central management of a network of event migration modules  104   a  for multiple users and/or hardware devices  102 . For example, the one or more backend event migration modules  104   b  and/or a backend server  110  may store downloaded event data for the event migration modules  104   a  centrally, may provide instructions for the event migration modules  104   a  to prompt a user to migrate a repeating event, or the like. A backend server  110  may include one or more servers located remotely from the hardware devices  102  and/or the one or more service providers  108 . A backend server  110  may include at least a portion of an event migration module  104 , may comprise hardware of an event migration module  104 , may store executable program code of an event migration module  104  in one or more non-transitory computer readable storage media, and/or may otherwise perform one or more of the various operations of an event migration module  104  described herein in order to migrate one or more repeating events to a different service provider  108 . 
     Once an event migration module  104  has migrated a repeating event to a different service provider  108 , the event migration module  104  may aggregate a subsequent set of events from the one or more servers  108  and may verify whether subsequent instances/occurrences of the repeating event remain migrated to the different service provider  108  in the subsequent set of events (e.g., using a similar analysis to that described above to determine whether the different service provider  108  is still performing the repeating event, or if the user has switched to another service provider  108 ). An event migration module  104  may re-prompt the user to migrate additional subsequent instances of the repeating event to the different service provider  108  if one or more of the subsequent instances of the repeating event have not remained migrated to the different service provider  108  (e.g., are no longer being performed/executed by the different service provider  108 ). 
     If a user denies or rejects a prompting to migrate a repeating event to a different service provider  108 , an event migration module  104  may iteratively and/or periodically re-prompt the user to migrate subsequent instances of the repeating event to the different service provider (e.g., until the user accepts a prompt and migrates the repeating event). In certain embodiments, an event migration module  104  may include an offer or other incentive to the user in a prompt, such as a discount on a cost of the repeating event, a rebate, a certain number of points, a coupon, a gift card, or the like. When iteratively re-prompting a user, an event migration module  104  may increase a value of an offer with each iteration, or the like. 
     In one embodiment, the event migration module  104  receives a user&#39;s electronic credentials for a third party service provider  108  from the user on a hardware device  102  of the user. In a further embodiment, the event migration module  104  may receive electronic credentials for a different user (e.g., from a different hardware device  102 , from a backend event migration module  104 , or the like), which may be encrypted and/or otherwise secured, so that an event migration module  104  may download data for the different user (e.g., downloading data for multiple users from a single user&#39;s hardware device  102 ). 
     For example, in the distributed/decentralized system  100 , if one user&#39;s hardware device  102  is turned off, asleep, out of battery, blocked by a third party service provider  108 , or the like, in certain embodiments, an event migration module  202  on a different user&#39;s hardware device  102  and/or on a backend server  110  may download data for the one user, using the one user&#39;s electronic credentials, and may send the data to the one user&#39;s hardware device  102 , may send an alert and/or push notification to the one user&#39;s hardware device  102 , or the like. In this manner, in one embodiment, a user may continue to aggregate data, receive alerts and/or push notifications, or the like, even if the user&#39;s own hardware device  102  is blocked, unavailable, or the like. In cooperation with one or more authentication modules  202 , the event migration modules  104   a ,  104   b , in certain embodiments, may communicate with each other using a secure and/or encrypted protocol, and/or may store electronic credentials in a secure and/or encrypted manner, so that a user may not see and/or access another user&#39;s electronic credentials, downloaded data, or other private and/or sensitive data. 
     In embodiments where an event migration module  104  comprises hardware (e.g., a semiconductor integrated circuit device such as an FPGA, an ASIC, or the like), the event migration module  104  may comprise dedicated security hardware for storing and/or processing electronic credentials, downloaded data, and/or other sensitive and/or private data, such as a secure cryptoprocessor (e.g., a dedicated computer on a chip or microprocessor embedded in a packaging with one or more physical security measures) which does not output decrypted data to an unsecure bus or storage, which stores cryptographic keys, a secure storage device; a trusted platform module (TPM) such as a TPM chip and/or TPM security device; a secure boot ROM or other type of ROM; an authentication chip; or the like. In another embodiment, the event migration module  104  may store and/or process electronic credentials, downloaded data, and/or other sensitive data in a secure and/or encrypted way using software and/or hardware of a user&#39;s existing hardware device  102  (e.g., encrypting data in RAM, NAND, and/or other general purpose storage) with or without dedicated security hardware. In certain embodiments, the event migration module  104  may encrypt and/or secure data (e.g., electronic credentials, downloaded data) associated with a first user that is received by, processed by, and/or stored by a second (e.g., different) user&#39;s hardware device  102  (e.g., from the first user&#39;s hardware device  102  over the data network  106  or the like), preventing the second user from accessing the first user&#39;s data while still allowing the first user&#39;s data to be downloaded and/or aggregated from a different user&#39;s hardware device  102 . 
     In one embodiment, as described above, electronic credentials may comprise one or more of a username and password, fingerprint scan, retinal scan, digital certificate, personal identification number (PIN), challenge response, security token, hardware token, software token, DNA sequence, signature, facial recognition, voice pattern recognition, bio-electric signals, two-factor authentication credentials, or other information whereby the event migration module  104  may authenticate and/or validate an identity of and/or an authorization of a user. 
     The event migration module  104 , in certain embodiments, may receive different credentials from a user for different accounts of the user with different third party service providers  108  (e.g., different social networks, different photo sharing sites, different financial institutions) so that the event migration module  104  may download, aggregate, and/or combine the user&#39;s data from the multiple different third party service providers  108 . In one embodiment, the event migration module  104 , instead of and/or in addition to receiving one or more passwords or other electronic credentials from a user, may manage and/or determine one or more passwords or other electronic credentials for a user for one or more third party service providers  108 . For example, in certain embodiments, the event migration module  104  may receive an initial set of electronic credentials (e.g., a username and a password) from a user for an account of the user with a third party service provider  108 , and the event migration module  104  may use the initial set of electronic credentials to access the user&#39;s account with the third party service provider  108  to set a new password, determined by the event migration module  104 . The event migration module  104 , in one embodiment, may determine passwords or other electronic credentials that are more secure than those typically created by and/or memorable to a user (e.g., longer, more numbers, greater variation between capital and lowercase letters, more frequently changed, or the like). 
     In one embodiment, an event migration module  104  accesses one or more servers  108  of one or more third party service providers  108 , from a hardware device  102  of a user and/or from a backend server  110 , using a user&#39;s electronic credentials from the event migration module  104  (e.g., for the user associated with the hardware device  102 , for a different user, or the like). An event migration module  104 , in certain embodiments, downloads data associated with a user (e.g., a user&#39;s social media posts, a user&#39;s photos, a user&#39;s financial transactions, or the like) from one or more servers  108  of one or more third party service providers  108  to a hardware device  102  of a user (e.g., of the user associated with the downloaded data, of a different user for processing and/or for transfer to the hardware device  102  of the user associated with the downloaded data, or the like) and/or to a backend server  110  associated with an event migration module  104 , instead of or in addition to downloading the data directly to a hardware device  102  of the user (e.g., based on an availability of the hardware device  102  of the user, to backup the data in a second location, or the like). 
     An event migration module  104 , in certain embodiments, may use a webpage interface of a server  108  of a third party service provider  108  to access the server  108  using a user&#39;s electronic credentials and/or to download data associated with the user. For example, in certain embodiments, an event migration module  104  may download/load a webpage from a server  108  of a third party service provider  108 , enter a username and password or other electronic credentials for a user into textboxes in a form on the webpage, submit the username and password or other electronic credentials using a submit button or other interface element of the webpage, and/or otherwise submit electronic credentials using a website to gain authorized access to data on the server  108  associated with the user. As described below, the pattern module  308  may receive and/or provide instructions enabling an event migration module  104  to access a server  108  (e.g., a location or method for submitting electronic credentials, or the like). 
     In response to successfully authenticating with and accessing a server  108  of a third party service provider  108  with a user&#39;s electronic credentials, an event migration module  104  may download data associated with the user (e.g., from a user&#39;s account or the like) from the server  108 , to a hardware device  102  associated with the user, to a backend server  110 , to a hardware device  102  of another user downloading the data in proxy for the user, or the like. As described below, in certain embodiments, the pattern module  308  may receive and/or provide instructions enabling an event migration module  104  to download data associated with a user from a server  108  of a third party service provider  108  (e.g., a URL or other link to a location for the data, a label or other identifier for locating the data within one or more webpages or other data structures, or the like). An event migration module  104 , in certain embodiments, may follow instructions from a pattern module  308  to authenticate and/or access data from one or more webpages from a server  108  in a screen scraping manner, parsing one or more webpages to locate an entry location and/or submit electronic credentials; to locate, download, and/or extract data associated with a user; or the like. 
     In one embodiment, an event migration module  104  sends or otherwise submits electronic credentials and/or receives or otherwise downloads data using an API or other access protocol of a server  108  of a third party service provider  108 . For example, an event migration module  104  may send a request in a format specified by and/or compatible with a server  108  (e.g., an API server  108 ) of a third party service provider  108 . The sent request may comprise electronic credentials for a user or a portion thereof (e.g., a username and/or a password), a subsequent request may comprise electronic credentials for a user or a portion thereof (e.g., in response to receiving an acknowledgment from the server  108  for the first request, or the like), and/or an event migration module  104  may use a different access protocol of a server  108 . 
     In response to a request for data from an event migration module  104  (e.g., in response to an event migration module  104  authenticating a user using an access protocol of a server  108 ), a server  108  of a third party service provider  108  may send and/or return data associated with a user (e.g., in one or more messages, packets, payloads, as a URL or other pointer to a location from where an event migration module  104  may retrieve the data, or the like). An event migration module  104 , in various embodiments, may receive data associated with a user directly from a server  108  of a third party service provider  108  over a data network  106 ; may receive a pointer, URL or other link to a location of data associated with a user from a server  108  of a third party service provider  108 ; may receive data associated with a user from another entity on a data network  106  (e.g., in response to a request from the server  108  of the third party service provider  108  to the other entity or the like); or may otherwise receive data associated with a user according to an access protocol of a third party service provider  108 . 
     In one embodiment, a third party service provider  108  provides an event migration module  104  with an API or other access protocol. In a further embodiment, an event migration module  104  may act as a wrapper for and/or a plugin or extension of, an application of a third party service provider  108  (e.g., a mobile application), and the application may have access to an API or other access protocol of the third party service provider  108 . In another embodiment, an event migration module  104  may be configured to use an API or other access protocol in a same manner as an application of a third party service provider  108  (e.g., a mobile application), through observation of the application of the third party service provider  108  or the like. In certain embodiments, an event migration module  104  may cooperate with an application of a third party service provider  108 , a web browser through which a user accesses services of a third party service provider  108 , or the like to access data associated with a user (e.g., accessing data already downloaded by an application and/or user, accessing a database or other data store of an application and/or web browser, scanning and/or screen scraping a web page of a third party service provider  108  as a user accesses the web page, or the like). 
     An event migration module  104 , in certain embodiments, may access different third party service providers  108  in different manners. For example, a first third party service provider  108  may grant an event migration module  104  with access to an API or other access protocol, while an event migration module  104  may use a web page interface (e.g., screen scraping) to access and download data from a second third party service provider  108 , or the like. In one embodiment, a remote backend server  110  may be associated with a first party service provider  110  (e.g., a vendor and/or provider of an event migration module  104 ) and an event migration module  104  may download data associated with a user from both the first party service provider  110  and from one or more third party service providers  108 , aggregating the data together so that the user may access the data in a single interface and/or application. For example, as described below with regard to the event migration module  104 , the event migration module  104  may provide a user access to the user&#39;s photos from multiple third party cloud storage providers  108  within a single photo application, may provide a user with access to the user&#39;s personal financial information within a single personal financial management application and/or online banking application, may provide a user with access to posts from multiple social networks within a single social networking application, or the like. 
     An event migration module  104 , in certain embodiments, may store downloaded and/or aggregated data independently from the one or more third party service providers  108 . For example, an event migration module  104  may store a user&#39;s downloaded and/or aggregated data on a hardware device  102  of the user, on a backend server  110  accessible by the user, or the like. In this manner, in certain embodiments, a user may control and/or access the user&#39;s data, even if a third party service provider  108  closes down or is not available, may use the user&#39;s data in any manner desired by the user even if the use is not supported by a third party service provider  108 , or the like. 
     An event migration module  104 , in one embodiment, in addition to and/or instead of downloading data from one or more third party service providers  108 , may upload data to and/or change one or more settings of one or more third party service providers  108 , in response to user input or the like. For example, in embodiments where the data comprises photos, an event migration module  104  may upload a photo from a hardware device  102  of the user to one or more third party service providers  110  (e.g., a downloaded photo that the user has edited on the hardware device  102  or the like). In embodiments where the data comprises social media posts or other content, an event migration module  104  may receive input from a user (e.g., a photo, a textual post, one or more emoji, a video, a document or other file, or the like) and upload the received input to one or more third party service providers  108  (e.g., social media sites or the like). In embodiments where the data comprises financial transactions or other financial data, an event migration module  104  may schedule a bill pay or other payment or funds transfer, remotely deposit a check (e.g., by uploading photos of the front and/or back of the check, or the like), and/or perform another action. 
     An event migration module  104  may update or change a user&#39;s account information with a third party service provider  108 , such as an account type or plan, credit card or other payment information associated with an account, a phone number or address or other contact information associated with an account, a password or other electronic credentials for an account, and/or other account information of a user for a third party service provider  108 . An event migration module  104  may update and/or upload data in a substantially similar manner to that described herein for downloading data (e.g., determining a user&#39;s electronic credentials for a third party service provider  108 , accessing a server  108  of the third party service provider  108 , uploading and/or providing data to the third party service provider  108 , or the like). 
     In one embodiment, the event migration module  104  provides a user&#39;s data downloaded by an event migration module  104 , from a hardware device  102  of a user (e.g., of the user associated with the downloaded data, of a different user) to another entity, such as a hardware device  102  of a user associated with the downloaded data (e.g., in response to the data being downloaded by a hardware device  102  of a different user, from one hardware device  102  of a user to another hardware device  102  of the same user), a remote server  110  or other remote device  102  unaffiliated with (e.g., not owned by, operated by, controlled by, or the like) the third party service provider  108  from which the data was downloaded, or the like. For example, the event migration module  104  may provide an API or other interface to provide a user&#39;s downloaded and/or aggregated data to a hardware device  102  of the user, to a backend event migration module  104   b , to a backend server  110 , to a different third party service provider  108 , to a different/second hardware device  102  of the user, or the like. 
     In certain embodiments, it may be transparent and/or substantially transparent to a user (e.g., not apparent) which hardware device  102 ,  110  has downloaded data associated with the user. For example, the event migration module  104  may provide downloaded data associated with a user from one hardware device  102  of the user to another hardware device  102  of the user, from a hardware device  102  of the user to a backend server  110  (e.g., from which the user may access the data using a web browser, an application, or the like), from a backend server  110  to a hardware device  102  of the user, or the like, allowing the user to access the data from a different location than the location to which the data was downloaded. 
     In certain embodiments, the event migration module  104  provides a graphical user interface (GUI) on a hardware device  102  of a user, and provides downloaded data associated with the user to the user through the GUI (e.g., allowing the user to view the data directly, providing one or more notifications and/or recommendations to the user based on the data, providing one or more tables or charts to the user based on the data, providing a summary of or one or more statistics related to the data, or the like). The event migration module  104 , in various embodiments, may provide a GUI to the user from the same hardware device  102  to which the data was downloaded, on a different hardware device  102  than the hardware device  102 ,  110  to which the data was downloaded, or the like. 
     For example, in one embodiments, where the data associated with a user comprises photos, the event migration module  104  may provide a photo management interface, a photo editing interface, or the like wherein the user may view and/or otherwise access the user&#39;s downloaded and/or aggregated photos. In a further embodiment, where the data associated with a user comprises the user&#39;s financial transaction history (e.g., purchases and/or other financial transactions downloaded from one or more financial institutions  108  such as banks, credit unions, lenders, or the like), the event migration module  104  may provide a personal financial management interface, with a list of transactions, one or more budgets, one or more financial goals, a debt management interface, a net worth interface, and/or another personal financial management interface wherein the user may view the user&#39;s downloaded and/or aggregated financial transaction history, and/or alerts or recommendations based thereon. In another embodiment, where the data associated with a user comprises social media posts, the event migration module  104  may provide a GUI comprising a stream, feed, and/or wall of social media posts for the user to view (e.g., downloaded and/or aggregated social media posts from multiple social networks  108 , from different contacts or friends of the user, or the like). 
     The event migration module  104 , in certain embodiments, may provide one or more access controls to a user, allowing the user to define which devices  102 , users, third party service providers  110 , or the like may access which data. For example, the event migration module  104  may provide an interface for a user to allow and/or restrict certain mobile applications, certain APIs for third party services, certain plugins or extensions, certain users, certain hardware devices  102 , and/or one or more other entities to access data downloaded for the user from one or more third party service providers  108  (e.g., with access controls by third party service provider  108  or other data source, by data type, by entity requesting access, and/or at another granularity). In this manner, the event migration module  104 , in certain embodiments, may comprise a local repository of aggregated data, which one or more other devices  102  and/or services may access and use, with a user&#39;s permission. 
       FIG. 2  depicts one embodiment of a method  200  for automated event migration. The method  200  begins and an event migration module  104  aggregates  202  a set of events from one or more servers  108  to a trusted hardware device  102  and/or  110 , different events of the set of events being associated with different service providers  108 . An event migration module  104  identifies  204 , on the trusted hardware device  102  and/or  110 , a repeating event from the set of events. An event migration module  104  prompts  206  a user to migrate subsequent instances of the repeating event from one service provider  204  to a different service provider  208  of the plurality of service providers  208 . An event migration module  104  migrates  208  the subsequent instances of the repeating event, using the user&#39;s electronic credentials, from the one service provider  108  to the different service provider  108  in response to the user accepting the prompting  206  and the method  700  ends. 
     The present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.